Skip to content

Auto expand "New PR" form#33971

Merged
wxiaoguang merged 4 commits into
go-gitea:mainfrom
wxiaoguang:fix-pr-form
Mar 24, 2025
Merged

Auto expand "New PR" form#33971
wxiaoguang merged 4 commits into
go-gitea:mainfrom
wxiaoguang:fix-pr-form

Conversation

@wxiaoguang

@wxiaoguang wxiaoguang commented Mar 22, 2025

Copy link
Copy Markdown
Contributor

Follow GitHub's behavior: use ?expand=1 to expand the "New PR" form

The old .Flash check is not needed anymore because now we use "fetch action form", no flash message.

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Mar 22, 2025
@wxiaoguang

Copy link
Copy Markdown
Contributor Author

image

image

image

image

@wxiaoguang wxiaoguang added the type/enhancement An improvement of existing functionality label Mar 22, 2025
@wxiaoguang wxiaoguang added this to the 1.24.0 milestone Mar 22, 2025
@silverwind

silverwind commented Mar 22, 2025

Copy link
Copy Markdown
Member

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 repo/pulls/new/branch which redirects to a auto-expanded compare page. I think it's using a ?-less URL so its easier to copy from terminal.

I would strongly prefer if we have that URL too and it could be used for this "Open PR" button.

@wxiaoguang

Copy link
Copy Markdown
Contributor Author

Will this also work for the links that are output when pushing to a new branch over SSH?

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.

@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Mar 22, 2025
@silverwind

silverwind commented Mar 24, 2025

Copy link
Copy Markdown
Member

Will this also work for the links that are output when pushing to a new branch over SSH?

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:

$ git checkout -b test
branch 'test' set up to track 'master' by rebasing.
Switched to a new branch 'test'
$ git commit --allow-empty -m 'test'
[test 3bbb14a] test
$ git push origin test
Enumerating objects: 1, done.
Counting objects: 100% (1/1), done.
Writing objects: 100% (1/1), 367 bytes | 183.00 KiB/s, done.
Total 1 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
remote:
remote: Create a new pull request for 'test':
remote:   https://gitea.com/org/repo/compare/master...test  <----
remote:
remote: . Processing 1 references
remote: Processed 1 references in total
To gitea.com:org/repo.git
 * [new branch]      test -> test

@silverwind

silverwind commented Mar 24, 2025

Copy link
Copy Markdown
Member

FYI, here is the same link that GitHub produces:

remote:
remote: Create a pull request for 'test2' on GitHub by visiting:
remote:      https://github.com/silverwind/gitea/pull/new/test2
remote:

When opening the link https://github.com/silverwind/gitea/pull/new/test2, it redirects to https://github.com/go-gitea/gitea/compare/main...silverwind:gitea:test2?expand=1, e.g. the expanded compare page.

@pull-request-size pull-request-size Bot added size/L and removed size/M labels Mar 24, 2025
@wxiaoguang

Copy link
Copy Markdown
Contributor Author

When opening the link https://github.com/silverwind/gitea/pull/new/test2, it redirects to https://github.com/go-gitea/gitea/compare/main...silverwind:gitea:test2?expand=1, e.g. the expanded compare page.

f1b1264

@silverwind silverwind left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome work, thanks

@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Mar 24, 2025
@wxiaoguang wxiaoguang enabled auto-merge (squash) March 24, 2025 14:05
@wxiaoguang wxiaoguang merged commit b1e326d into go-gitea:main Mar 24, 2025
@wxiaoguang wxiaoguang deleted the fix-pr-form branch March 24, 2025 14:31
zjjhot added a commit to zjjhot/gitea that referenced this pull request Mar 26, 2025
* 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)
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Jun 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/enhancement An improvement of existing functionality

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants