pjp opened a new pull-request against the project: `fedora-budget` that you are following: `` F28 release part Bengaluru entry ``
To reply, visit the link below or just reply to this email https://pagure.io/fedora-budget/pull-request/55
bex commented on the pull-request: `F28 release part Bengaluru entry` that you are following: `` Looking at this PR, I see the same issues. I wonder if this commit
https://pagure.io/fork/pjp/fedora-budget/c/705b514c78eb595471f7715ad27b997e6...
is the issue.
Can you do a rebase?
Assuming you've mapped the upstream as a remote named upstream:
git checkout <your branch> git fetch upstream git pull --rebase upstream/master git push -f origin <your branch>
This PR is coming from master, which is generally not the best place to originate a PR.
Happy to work with you in real-time on this. ``
To reply, visit the link below or just reply to this email https://pagure.io/fedora-budget/pull-request/55
jflory7 commented on the pull-request: `F28 release part Bengaluru entry` that you are following: `` This pull request was opened in April 2018 and was handled in a previous fiscal year, when @bex was FCAIC. So, I am going to close this PR since it changes 73+ different files from multiple different fiscal years, which I don't think was intended. ``
To reply, visit the link below or just reply to this email https://pagure.io/fedora-budget/pull-request/55
jflory7 closed without merging a pull-request against the project: `fedora-budget` that you are following.
Closed pull-request:
`` F28 release part Bengaluru entry ``
budget-devel@lists.fedoraproject.org
-
Brian Exelbierd (bex) -
Justin W. Flory
-
P J P