-
Notifications
You must be signed in to change notification settings - Fork 36
Update Contributing Document - 18 #908
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
base: 18
Are you sure you want to change the base?
Conversation
This PR updates the contributing guide.
| docker run --rm -v $(pwd):/docs perconalab/pmm-doc-md mkdocs build | ||
| git add . | ||
| git commit -m "<my_fixes>" | ||
| git push -u origin <my_branch_name> |
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.
git push -u origin <my_branch_name>. Otherwise upstream repo is unaware of this change
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.
Shouldn't users push the branch to their fork (origin), and not to upstream? If the user does a pull request (step 7), then the upstream repository identifies the changes.
It's the way I am pushing upstream PRs as well, did I understand this incorrectly?
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.
@Andriciuc I followed your instructions from the very first step, and I managed to create a PR with git push -u origin <my_branch_name>.
Co-authored-by: Anastasia Alexandrova <anastasia.alexandrova@percona.com>
alina-derkach-oaza
left a comment
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.
LGTM
This PR updates the contributing guide.