-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto expand "New PR" form #33971
Auto expand "New PR" form #33971
Conversation
Will this also work for the links that are output when pushing to a new branch over SSH? GitHub uses a special URL scheme like I would strongly prefer if we have that URL too and it could be used for this "Open PR" button. |
I do not know where it is (I don't use it). So feel free to add it in this PR or improve it in the future. |
It's the message that shows for the first time when pushing to a branch:
|
FYI, here is the same link that GitHub produces:
When opening the link |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome work, thanks
* giteaofficial/main: Enable color output in govulncheck (go-gitea#34012) Update Makefile test comments (go-gitea#34013) Move duplicated functions (go-gitea#33977) Git client will follow 301 but 307 (go-gitea#34005) Prepare common tmpl functions in a middleware (go-gitea#33957) Update go mod dependencies (go-gitea#33988) Fix some migration and repo name problems (go-gitea#33986) [skip ci] Updated translations via Crowdin Use filepath.Join instead of path.Join for file system file operations (go-gitea#33978) Add changelog for 1.23.6 (go-gitea#33975) Fix incorrect code search indexer options (go-gitea#33992) Auto expand "New PR" form (go-gitea#33971) Move ParseBool to optional (go-gitea#33979)
Follow GitHub's behavior: use
?expand=1
to expand the "New PR" formThe old
.Flash
check is not needed anymore because now we use "fetch action form", no flash message.