Skip to content
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

Meta: move general guidelines to the whatwg/meta repo #2295

Merged
merged 1 commit into from
Jan 27, 2017

Conversation

foolip
Copy link
Member

@foolip foolip commented Jan 25, 2017

The HTML Standard is quite complex and people notice minor and larger issues with it all the time. We'd love your help fixing these. Pull requests for typographical and grammar errors are also most welcome.

We label [good first bugs](https://github.com/whatwg/html/labels/good%20first%20bug) that you could help us fix, to get a taste for how to submit pull requests, how the build process works, and so on.

We'd be happy to mentor you through this process. If you're interested and need help getting started, leave a comment on the issue or bug, or ask around [on IRC](https://wiki.whatwg.org/wiki/IRC). The [WHATWG FAQ](https://wiki.whatwg.org/wiki/FAQ) may also be helpful.

### Pull requests
## Pull requests

In short, change `source` and submit your patch, with a [good commit message](https://github.com/erlang/otp/wiki/Writing-good-commit-messages).
Copy link
Member Author

Choose a reason for hiding this comment

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

I made no attempt to generalize and move this. Should I?

Copy link
Member

Choose a reason for hiding this comment

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

No, seems OK to keep here.

foolip added a commit to whatwg/meta that referenced this pull request Jan 26, 2017
These are extracted from HTML, with a corresponding PR:
whatwg/html#2295
@foolip foolip requested a review from zcorpan January 26, 2017 04:40
This checks out the PR's commits, rebases them on `master`, then fast-forwards `master` to include them.

The `git push --force` line here ensures that the original branch gets updated to sit on top of `master` as well. This ensures GitHub can automatically figure out that the commits were merged, and thus automatically close the pull request with a nice purple "merged" status. So at this point you can do a `git push origin master` to push the changes, and GitHub will close the PR and mark it as merged.
These are the guidelines for the team maintaining the HTML Standard. First see the [WHATWG maintainer guidelines](meta/blob/master/CONTRIBUTING.md).
Copy link
Member

Choose a reason for hiding this comment

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

wrong link?

Copy link
Member Author

Choose a reason for hiding this comment

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

Oops, fixed, and I'll now squash into a single commit for final review.

@foolip foolip force-pushed the general-guidelines branch from fa8dd33 to 03145e0 Compare January 26, 2017 14:44
@foolip foolip changed the title Meta: move tests and other general guidlines to meta/ Meta: move general guidelines to the whatwg/meta repo Jan 26, 2017
foolip added a commit to whatwg/meta that referenced this pull request Jan 27, 2017
These are extracted from HTML, with a corresponding PR:
whatwg/html#2295
@foolip foolip merged commit 1e11711 into master Jan 27, 2017
@foolip foolip deleted the general-guidelines branch January 27, 2017 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants