Skip to content

[CONTRIBUTING.md] Clarify that PRs should originate from your own fork #10009

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

Merged
merged 1 commit into from
Feb 28, 2024

Conversation

bramus
Copy link
Contributor

@bramus bramus commented Feb 28, 2024

Minor update to clarify that PRs should originate from your own fork. This is something I had to find out when filing one of my first PRs – I had created a branch in the w3c/csswg-drafts repo, upon which I was told that this isn’t how things are done here.

@svgeesus
Copy link
Contributor

It was much more of an issue when the GitHub to Mercurial two-way bridge was still an important part of some people's workflow because any branch here would break things. AFAIK that is no longer the case.

Copy link
Contributor

@svgeesus svgeesus left a comment

Choose a reason for hiding this comment

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

Seems ok to me, though the rationale is mainly historical at this point.

@svgeesus svgeesus merged commit ba68cb3 into w3c:main Feb 28, 2024
@tabatkins
Copy link
Member

Yeah, maintaining branches either here or in your personal fork are both fine. The main benefit of keeping them in your own fork is it keeps our list of branches smaller, so you don't have as many things cluttering up the branches list. (In other words, I'm fine with keeping this advice here.)

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