1Test submission is via the typical GitHub workflow. 2 3* Fork the [GitHub repository][repo] (and make sure you're still relatively in 4sync with it if you forked a while ago) 5 6* Create a branch for your changes. Being a key of effective Git flow, it is 7strongly recommended that the **topic branch** tradition be followed here, 8i.e. the branch naming convention is based on the "topic" you will be working 9on, e.g. `git checkout -b topic-name` 10 11* Make your changes 12 13* Run the `lint` script in the root of your checkout to detect common 14 mistakes in test submissions. This will also be run after submission 15 and any errors will prevent your PR being accepted. If it detects an 16 error that forms an essential part of your test, edit the list of 17 exceptions stored in `tools/lint/lint.whitelist`. 18 19* Commit your changes. 20 21* Push your local branch to your GitHub repository. 22 23* Using the GitHub UI create a Pull Request for your branch. 24 25* When you get review comments, make more commits to your branch to 26 address the comments (**note**: Do *not* rewrite existing commits using 27 e.g. `git commit --amend` or `git rebase -i`. The review system 28 depends on the full branch history). 29 30* Once everything is reviewed and all issues are addressed, your pull 31 request will be automatically merged. 32 33For detailed guidelines on setup and each of these steps, please refer to the 34[Github Test Submission][github101] documentation. 35 36Hop on to [irc or the mailing list][discuss] if you have an 37issue. There is no need to announce your review request, as soon as 38you make a Pull Request GitHub will inform interested parties. 39 40[repo]: https://github.com/w3c/web-platform-tests/ 41[github101]: ./github-101.html 42[discuss]: /discuss.html 43