reserve .well-known username #7639
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zeripath
approved these changes
Jul 26, 2019
GiteaBot
added
the
lgtm/need 1
mrsdizzie
approved these changes
Jul 26, 2019
GiteaBot
added
lgtm/done
|
I don't understand why but it appears that make swagger-generate and then commit the changes needs to performed. |
|
Upstream swagger has changed output which we resolved in 1.9 and master. As we are releasing 1.9 soon I’m not sure this needs a backport to 1.8 |
|
We will just need to indicate that we strongly suggest to update to 1.9 branch due to security bug that will not be fixed in 1.8. |
|
@sapk I'm writing the changelog for 1.9.0 right now, so I'm going to close this PR. |
project-mirrors-bot-tu bot
pushed a commit
to project-mirrors/forgejo-as-gitea-fork
that referenced
this pull request
May 15, 2025
Currently, if you have a mirrored repo, the button on the "branches" page to create a new branch is available to be pressed. Once you name your new branch and click submit, you get a 404 page that doesn't explain what went wrong. As new branch creation is not supported on mirrored repos, let's just take that button away if the repo is a mirror. This is already done for archived repos, so we just need to add another check. Fixes go-gitea#7639. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/7640 Reviewed-by: Otto <[email protected]> Co-authored-by: John Moon <[email protected]> Co-committed-by: John Moon <[email protected]> (cherry picked from commit 09f7dbe)
project-mirrors-bot-tu bot
pushed a commit
to project-mirrors/forgejo-as-gitea-fork
that referenced
this pull request
May 15, 2025
Currently, if you have a mirrored repo, the button on the "branches" page to create a new branch is available to be pressed. Once you name your new branch and click submit, you get a 404 page that doesn't explain what went wrong. As new branch creation is not supported on mirrored repos, let's just take that button away if the repo is a mirror. This is already done for archived repos, so we just need to add another check. Fixes go-gitea#7639. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/7640 Reviewed-by: Otto <[email protected]> Co-authored-by: John Moon <[email protected]> Co-committed-by: John Moon <[email protected]>
project-mirrors-bot-tu bot
pushed a commit
to project-mirrors/forgejo-as-gitea-fork
that referenced
this pull request
May 16, 2025
…o-gitea#7869) **Backport:** https://codeberg.org/forgejo/forgejo/pulls/7640 Currently, if you have a mirrored repo, the button on the "branches" page to create a new branch is available to be pressed. Once you name your new branch and click submit, you get a 404 page that doesn't explain what went wrong. As new branch creation is not supported on mirrored repos, let's just take that button away if the repo is a mirror. This is already done for archived repos, so we just need to add another check. Fixes go-gitea#7639. Co-authored-by: John Moon <[email protected]> Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/7869 Reviewed-by: Otto <[email protected]> Co-authored-by: forgejo-backport-action <[email protected]> Co-committed-by: forgejo-backport-action <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
backport of #7637