Skip to content

Conversation

@Andriciuc
Copy link
Contributor

This PR updates the contributing guide.

This PR updates the contributing guide.
@Andriciuc Andriciuc changed the title Update Contributing Document Update Contributing Document - 18 Jan 12, 2026
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>
Copy link
Contributor

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

Copy link
Contributor Author

@Andriciuc Andriciuc Jan 15, 2026

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?

Copy link
Contributor

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>
Copy link
Contributor

@alina-derkach-oaza alina-derkach-oaza left a comment

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants