github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Change Git Release description #2213

New Issue
Closed
opened 2025-11-02 04:27:26 -06:00 by GiteaMirror · 16 comments
GiteaMirror commented 2025-11-02 04:27:26 -06:00
Owner
Copy Link

Originally created by @thimmy687 on GitHub (Aug 17, 2018).

  • Gitea version (or commit ref): 1.5.0
  • Git version: 2.18.0
  • Operating system: Windows
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Can't edit description of existing releases.

...

Screenshots

Originally created by @thimmy687 on GitHub (Aug 17, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.5.0 - Git version: 2.18.0 - Operating system: Windows - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description Can't edit description of existing releases. ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/staleissue/needs-feedback labels 2025-11-02 04:27:26 -06:00
GiteaMirror commented 2025-11-02 04:27:28 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Aug 17, 2018):

Can not seem to reproduce that. When clicking on edit link that is near release title I can edit description and title

@lafriks commented on GitHub (Aug 17, 2018): Can not seem to reproduce that. When clicking on edit link that is near release title I can edit description and title
GiteaMirror commented 2025-11-02 04:27:29 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 13, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 13, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:27:29 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 20, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 20, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
GiteaMirror commented 2025-11-02 04:27:30 -06:00
Author
Owner
Copy Link

@relikd commented on GitHub (Dec 13, 2019):

I do have the same problem. A repository I had up and running on github. All releases (created via github GUI) can't be edited. There isn't even a clickable link. I can only open the tag which will show the tree state.

Gitea version 1.10.0 built with GNU Make 4.2.1, go1.13.4 : bindata, sqlite, pam

Exact same view as if I were not logged in.

@relikd commented on GitHub (Dec 13, 2019): I do have the same problem. A repository I had up and running on github. All releases (created via github GUI) can't be edited. There isn't even a clickable link. I can only open the tag which will show the tree state. `Gitea version 1.10.0 built with GNU Make 4.2.1, go1.13.4 : bindata, sqlite, pam` Exact same view as if I were not logged in.
GiteaMirror commented 2025-11-02 04:27:30 -06:00
Author
Owner
Copy Link

@relikd commented on GitHub (Dec 14, 2019):

Are tags handled differently than releases?
You can try with a vanilla gitea installation and this repository: https://github.com/relikd/baRSS

In the installation step I disabled all external services (Local Mode is enabled).
Also disabled Self-Registration.

@relikd commented on GitHub (Dec 14, 2019): Are tags handled differently than releases? You can try with a vanilla gitea installation and this repository: https://github.com/relikd/baRSS In the installation step I disabled all external services (Local Mode is enabled). Also disabled Self-Registration.
GiteaMirror commented 2025-11-02 04:27:31 -06:00
Author
Owner
Copy Link

@relikd commented on GitHub (Dec 14, 2019):

@lafriks
And if I open the edit URL directly, it opens the edit form field (compared to a non-existing tag where I get a 404). However, after I click on save I get the 404 error and nothing is updated.
(also notice this "wrong" edit form does not show the branch / commit selection)

screen

@relikd commented on GitHub (Dec 14, 2019): @lafriks And if I open the edit URL directly, it opens the edit form field (compared to a non-existing tag where I get a 404). However, after I click on save I get the 404 error and nothing is updated. (also notice this "wrong" edit form does not show the branch / commit selection) ![screen](https://user-images.githubusercontent.com/1321720/70848624-d06c0080-1e74-11ea-8c15-23f59c42c1b0.png)
GiteaMirror commented 2025-11-02 04:27:31 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 14, 2019):

@relikd could you reproduce that on https://try.gitea.io ?

@lunny commented on GitHub (Dec 14, 2019): @relikd could you reproduce that on https://try.gitea.io ?
GiteaMirror commented 2025-11-02 04:27:32 -06:00
Author
Owner
Copy Link

@relikd commented on GitHub (Dec 14, 2019):

yup. Migrate from this URL: https://github.com/relikd/baRSS

@relikd commented on GitHub (Dec 14, 2019): yup. Migrate from this URL: https://github.com/relikd/baRSS
GiteaMirror commented 2025-11-02 04:27:32 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 14, 2019):

https://try.gitea.io/lunny/baRSS/releases I didn't get 404.

@lunny commented on GitHub (Dec 14, 2019): https://try.gitea.io/lunny/baRSS/releases I didn't get 404.
GiteaMirror commented 2025-11-02 04:27:33 -06:00
Author
Owner
Copy Link

@relikd commented on GitHub (Dec 14, 2019):

How is this even possible? Here, with and without mirror. Both not working:

https://try.gitea.io/asdglkashdgask/baRSS/releases
https://try.gitea.io/asdglkashdgask/baRSS2/releases

And I get the same if I manually git push to a fresh gitea repo.

EDIT: you got even issues etc. Thats all empty for my repos too...

@relikd commented on GitHub (Dec 14, 2019): How is this even possible? Here, with and without mirror. Both not working: https://try.gitea.io/asdglkashdgask/baRSS/releases https://try.gitea.io/asdglkashdgask/baRSS2/releases And I get the same if I manually git push to a fresh gitea repo. EDIT: you got even issues etc. Thats all empty for my repos too...
GiteaMirror commented 2025-11-02 04:27:33 -06:00
Author
Owner
Copy Link

@mrsdizzie commented on GitHub (Dec 14, 2019):

@relikd you need to do a migration with your Github credentials to have the option to migrate issues and releases (among other things)

Push and mirror will only have what is stored in git itself which is the code and tags.

You can edit releases but not tags, so you would need to do a full migration from Github to have releases (as @lunny has done in that example). Migration is what copies over anything not stored in git from Github.

So new->migration and then put in the repo URL and your Github credentials in order to see the extra migration options.

@mrsdizzie commented on GitHub (Dec 14, 2019): @relikd you need to do a *migration* with your Github credentials to have the option to migrate issues and releases (among other things) Push and mirror will only have what is stored in git itself which is the code and tags. You can edit releases but not tags, so you would need to do a full migration from Github to have releases (as @lunny has done in that example). Migration is what copies over anything not stored in git from Github. So new->migration and then put in the repo URL and your Github credentials in order to see the extra migration options.
GiteaMirror commented 2025-11-02 04:27:34 -06:00
Author
Owner
Copy Link

@relikd commented on GitHub (Dec 14, 2019):

Alright, but then why do I need to use my credentials at all? The API is publicly accessible even without credentials, e.g.: https://api.github.com/repos/relikd/baRSS/releases
I'm hesitant to store my login credential on my publicly accessible server especially when there is no real need for.

Further, If I import the repo via manual push all tags create a non-editable release.
Then how should I modify that information afterwards?

@relikd commented on GitHub (Dec 14, 2019): Alright, but then why do I need to use my credentials at all? The API is publicly accessible even without credentials, e.g.: https://api.github.com/repos/relikd/baRSS/releases I'm hesitant to store my login credential on my publicly accessible server especially when there is no real need for. Further, If I import the repo via manual push all tags create a non-editable release. Then how should I modify that information afterwards?
GiteaMirror commented 2025-11-02 04:27:35 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 15, 2019):

@relikd Because github will limit the request limitation if you are using a public credential. You will fail after serval requests.

@lunny commented on GitHub (Dec 15, 2019): @relikd Because github will limit the request limitation if you are using a public credential. You will fail after serval requests.
GiteaMirror commented 2025-11-02 04:27:35 -06:00
Author
Owner
Copy Link

@relikd commented on GitHub (Jan 28, 2020):

Is it possible to use github access tokens instead?
Either a token per user or a single admin token for all users?
OR at the very least, use a redirect to github to authenticate?

Again, I find it very shady to input my plain-text password into a third party application...

@relikd commented on GitHub (Jan 28, 2020): Is it possible to use github access tokens instead? Either a token per user or a single admin token for all users? OR at the very least, use a redirect to github to authenticate? Again, I find it very shady to input my plain-text password into a third party application...
GiteaMirror commented 2025-11-02 04:27:36 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 28, 2020):

@relikd Yes, an access token is OK.

@lunny commented on GitHub (Jan 28, 2020): @relikd Yes, an access token is OK.
GiteaMirror commented 2025-11-02 04:27:37 -06:00
Author
Owner
Copy Link

@relikd commented on GitHub (Jan 28, 2020):

Perfect. I can't find a documentation on what is the minimum set of token scopes. public_repo does not seem to be enough, gitea failes with "Migrating from X failed."

@relikd commented on GitHub (Jan 28, 2020): Perfect. I can't find a documentation on what is the minimum set of token scopes. `public_repo` does not seem to be enough, gitea failes with "Migrating from X failed."
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/needs-feedback issue/stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2213
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?