Hexagon/Base64 Contribution guide

New contributor guide

To get an overview of the project, read the README. Here are some resources to help you get started with open source contributions:

Getting started

Issues

Create a new issue

If you spot a problem with base64, 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. If you find an issue to work on, drop a note in the comments asking to assign it to you. After that, you can start with your changes and open a PR with a fix.

Make Changes

Setting up the environment

We recommend using VS Code with eslint extensions. It will automatically check your code against the defined rules.

Fork the repository.
- Using GitHub Desktop:
  - Getting started with GitHub Desktop will guide you through setting up Desktop.
  - Once Desktop is set up, you can use it to fork the repo!
- Using the command line:
- Fork the repo so that you can make your changes without affecting the original project until you’re ready to merge them.
Install or update to Node.js v18.
Create a working branch feature/my-cool-feature or bugfix/issue-14 and start with your changes!

Commit your update

Please run deno task build before committing, to make sure that every test and check passes.

See deno.json scripts section for all available scripts.

Then, commit the changes once you are happy with them.

Pull Request

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

Don’t forget to link PR to issue if you are solving one.
Enable the checkbox to allow maintainer edits so that the branch can be updated for a merge. Once you submit your PR, a team member will review your proposal. We may ask questions or request for additional information.
We may ask for changes to be made before a PR can be merged 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. The changes will automatically be reflected in the PR.
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.

Success!

This guide is based on GitHub Docs CONTRIBUTING.md