Skip to content
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

Fix new pull request link #3133

Merged
merged 3 commits into from
Dec 13, 2017
Merged

Fix new pull request link #3133

merged 3 commits into from
Dec 13, 2017

Conversation

ethantkoenig
Copy link
Member

Fixes #3131 and #3132. Now, clicking the "New request button" creates a pull request whose head is the currently-viewed branch (like Github does). The button is not shown when viewing a tag or commit.

@codecov-io
Copy link

codecov-io commented Dec 10, 2017

Codecov Report

Merging #3133 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #3133      +/-   ##
==========================================
- Coverage   34.73%   34.72%   -0.01%     
==========================================
  Files         276      276              
  Lines       39949    39946       -3     
==========================================
- Hits        13876    13873       -3     
  Misses      24076    24076              
  Partials     1997     1997
Impacted Files Coverage Δ
modules/context/repo.go 59.64% <ø> (-0.24%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e693fda...19afce7. Read the comment docs.

@tboerger tboerger added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Dec 10, 2017
@lunny
Copy link
Member

lunny commented Dec 10, 2017

If click on the baserepo?

@lafriks lafriks added this to the 1.4.0 milestone Dec 10, 2017
@ethantkoenig
Copy link
Member Author

@lunny I'm not sure what you're asking

@lafriks
Copy link
Member

lafriks commented Dec 10, 2017

@ethantkoenig if you click on new pull request in base repository (to create PR between it's branches)

@ethantkoenig
Copy link
Member Author

If you click on the button in the base repo, you'll create a PR from whatever branch you're currently looking at (in the base repo) to the default branch (presumably master) in the base repo.

@lafriks
Copy link
Member

lafriks commented Dec 12, 2017

Tested and both cases seems to be working just as expected. LGTM

@tboerger tboerger 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 Dec 12, 2017
@lunny
Copy link
Member

lunny commented Dec 13, 2017

LGTM

@tboerger tboerger 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 Dec 13, 2017
@lunny lunny merged commit 0b77dbc into go-gitea:master Dec 13, 2017
@ethantkoenig ethantkoenig deleted the fix/pr_link branch December 15, 2017 03:47
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
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/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

404 when clicking "New pull request".
6 participants