-
-
Notifications
You must be signed in to change notification settings - Fork 597
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
Add sync a fork branch with the upstream repository #1084
Conversation
DAGpro
commented
Sep 18, 2022
Q | A |
---|---|
New feature? | ✔️ |
Fixed issues | #1083 |
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.
@DAGpro - You'll want to fix CI issues here. Looks like a basic lint issue so the test suite can move forward.
0b526e0
to
88e1b35
Compare
The commit message must mention the issue? |
The squash merge normally renames the commit anyway, so don't think that important. You still have some linting issues btw - https://github.styleci.io/analyses/xgBanO |
53a822f
to
369de6b
Compare
369de6b
to
184826b
Compare
@iBotPeaches now no problem to merge? |
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.
Thanks for the PR @DAGpro!
Can you also add a test for this method, see: https://github.com/KnpLabs/php-github-api/blob/master/test/Github/Tests/Api/RepoTest.php. And add a docs entry so it is documented, see https://github.com/KnpLabs/php-github-api/blob/master/doc/repos.md
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.
One small remark and then it's ready to merge!
Thanks @DAGpro! And congrats on your first contribution! 🎉 |