diff options
author | Vincent Ambo <tazjin@google.com> | 2019-08-15T15·11+0100 |
---|---|---|
committer | Vincent Ambo <tazjin@google.com> | 2019-08-15T15·11+0100 |
commit | 128875b501bc2989617ae553317b80faa556d752 (patch) | |
tree | 9b32d12123801179ebe900980556486ad4803482 /third_party/bazel/rules_haskell/CONTRIBUTING.md | |
parent | a20daf87265a62b494d67f86d4a5199f14394973 (diff) |
chore: Remove remaining Bazel-related files r/31
Diffstat (limited to 'third_party/bazel/rules_haskell/CONTRIBUTING.md')
-rw-r--r-- | third_party/bazel/rules_haskell/CONTRIBUTING.md | 36 |
1 files changed, 0 insertions, 36 deletions
diff --git a/third_party/bazel/rules_haskell/CONTRIBUTING.md b/third_party/bazel/rules_haskell/CONTRIBUTING.md deleted file mode 100644 index 848cbb1b9663..000000000000 --- a/third_party/bazel/rules_haskell/CONTRIBUTING.md +++ /dev/null @@ -1,36 +0,0 @@ -# Contributing to Bazel - -## Contributor License Agreement - -Contributions to this project must be accompanied by a Contributor License -Agreement. You (or your employer) retain the copyright to your contribution, -this simply gives us permission to use and redistribute your contributions as -part of the project. Head over to <https://cla.developers.google.com/> to see -your current agreements on file or to sign a new one. - -You generally only need to submit a CLA once, so if you've already submitted one -(even if it was for a different project), you probably don't need to do it -again. - -## Contribution process - -1. Explain your idea and discuss your plan with members of the team. - The best way to do this is to create an [issue][issue-tracker] or - comment on an existing issue. -1. Prepare a git commit with your change. Don't forget to - add [tests][tests]. Run the existing tests with `bazel test //...`. - Update [README.md](./README.md) if appropriate. -1. [Create a pull request](https://help.github.com/articles/creating-a-pull-request/). - This will start the code review process. **All submissions, - including submissions by project members, require review.** -1. You may be asked to make some changes. You'll also need to sign the - CLA at this point, if you haven't done so already. Our continuous - integration bots will test your change automatically on supported - platforms. Once everything looks good, your change will be merged. - -[issue-tracker]: https://github.com/tweag/rules_haskell/issues -[tests]: https://github.com/tweag/rules_haskell/tree/master/tests - -## Setting up your development environment - -Read how to [set up your development environment](https://bazel.build/contributing.html) |