Skip to content

Latest commit

 

History

History
50 lines (36 loc) · 2.79 KB

CONTRIBUTING.md

File metadata and controls

50 lines (36 loc) · 2.79 KB
Raw

Contributing

Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.

Contributions to this project are released to the public under the project's open source license.

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

Scope

We want to use this repository to distribute the best data pre-processing and loading pipeline for the CodeSearchNet dataset. As we anticipate other data scientists and researchers to design many custom architectures and use frameworks other than Tensorflow, we do not want to update the models in this repository beyond the simple baselines we originally released. Therefore, we are accepting pull requests for the following items:

  • Improvements of the data pre-processing pipeline (e.g. better cleaning heuristics, new supported languages, etc.)
  • Documentation updates that help others use the dataset
  • Documentation updates with links to your project(s) where improvements to the baseline have been made
  • Bug fixes for bugs in the baseline models (i.e., not better hyperparameter settings)

Please open an issue if you are unsure regarding the best course of action.

Submitting a pull request

  1. Fork and clone the repository
  2. Configure and install the dependencies: script/bootstrap
  3. Make sure the tests pass on your machine: see azure-pipelines.yml to see tests we are currently running.
  4. Create a new branch: git checkout -b my-branch-name
  5. Make your change, add tests, and make sure the tests still pass.
  6. Push to your fork and submit a pull request
  7. Pat your self on the back and wait for your pull request to be reviewed and merged.

Here are a few things you can do that will increase the likelihood of your pull request being accepted:

  • Follow the style guide.
  • Write tests.
  • Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
  • Write a good commit message.

Resources