Explanation for missing releases (#3823)
Searched for missing releases/tags for some time, thought the solution might be helpful to others
This commit is contained in:
		
							parent
							
								
									725835b5b1
								
							
						
					
					
						commit
						48b19a5d14
					
				
					 1 changed files with 14 additions and 0 deletions
				
			
		|  | @ -66,3 +66,17 @@ In this case, look into the following settings: | ||||||
|     * `usermod` or `chsh` can be used to modify this. |     * `usermod` or `chsh` can be used to modify this. | ||||||
|   * Ensure that the `gitea serv` command in `.ssh/authorized_keys` uses the |   * Ensure that the `gitea serv` command in `.ssh/authorized_keys` uses the | ||||||
|     correct configuration file. |     correct configuration file. | ||||||
|  | 
 | ||||||
|  | ## Missing releases after migrating repository with tags | ||||||
|  | 
 | ||||||
|  | To migrate an repository *with* all tags you need to do two things | ||||||
|  | 
 | ||||||
|  | * Push tags to the repository: | ||||||
|  | ``` | ||||||
|  |  git push --tags | ||||||
|  |  ``` | ||||||
|  |   | ||||||
|  |  * (Re-)sync tags of all repositories within gitea: | ||||||
|  |  ``` | ||||||
|  |  gitea admin repo-sync-releases | ||||||
|  |  ``` | ||||||
|  |  | ||||||
		Loading…
	
		Reference in a new issue