Skip to content

Latest commit

 

History

History
54 lines (31 loc) · 3.66 KB

CONTRIBUTING.md

File metadata and controls

54 lines (31 loc) · 3.66 KB
Raw

Welcome to ENS docs contributing guide

Thank you for investing your time in contributing to our documentation! Any contribution you make will be reflected on docs.ens.domains ✨.

In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.

Getting started

This guide will walk you through the process of contributing to the ENS docs. If you are new to GitHub, you can checkout this GitHub tutorial to get started.

Issues

Create a new issue

If you spot a problem with the docs, search if an issue already exists. If a related issue doesn't exist, you can open a new issue using a relevant issue form.

Solve an issue

Scan through our existing issues to find one that interests you. You can narrow down the search using labels as filters. As a general rule, we don't assign issues to anyone. If you find an issue to work on, you are welcome to open a PR with a fix.

Make Changes

Make changes in the UI

Click Make a contribution at the bottom of any docs page to make small changes such as a typo, sentence fix, or a broken link. This takes you to the .md file where you can make your changes and create a pull request for a review.

Make changes locally

  1. Fork the repository.

  2. (Optional) If you are making any code changes. Install or update to Node.js, or run nvm use if using Node Version Manager. For more information, see the development guide.

  3. Create a working branch and start with your changes!

Commit your update

Commit the changes once you are happy with them. Upon creating a Pull Request your code will automatically be tested ⚡.

Pull Request

When you're finished with the changes, create a pull request, also known as a PR.

  • Fill the "Ready for review" template so that we can review your PR. This template helps reviewers understand your changes as well as the purpose of your pull request.
  • Don't forget to link PR to issue if you are solving one.
  • Enable the checkbox to allow maintainer edits so the branch can be updated for a merge. Once you submit your PR, a Docs team member will review your proposal. We may ask questions or request additional information.
  • We may ask for changes to be made before a PR can be merged, either using suggested changes or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.
  • As you update your PR and apply changes, mark each conversation as resolved.
  • If you run into any merge issues, checkout this git tutorial to help you resolve merge conflicts and other issues.

Your PR is merged!

Congratulations 🎉🎉 The ENS team thanks you ✨.

Once your PR is merged, your contributions will be publicly visible on the ENS Docs.