actions/docker-buildx
actions/docker-buildx
3
0
Fork 0
mirror of https://gitea.com/docker/setup-buildx-action.git synced 2024-11-25 10:59:35 +01:00
Code Issues Projects Activity Pipelines
docker-buildx/.github/CONTRIBUTING.md
Tõnis Tiigi 41ae3d0e5f
Add container based dev flow (#4) 
* add container based dev flow

Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>

* Fix yarn test for container based dev flow

Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>

* Update contributing guidelines and test workflow

Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>

Co-authored-by: CrazyMax <crazy-max@users.noreply.github.com>
2020-08-26 23:48:38 +00:00

2 KiB
Raw Permalink Blame History

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.

Submitting a pull request

  1. Fork and clone the repository
  2. Configure and install the dependencies: yarn install
  3. Create a new branch: git checkout -b my-branch-name
  4. Make your change, add tests, and make sure the tests still pass
  5. Run pre-checkin: yarn run pre-checkin
  6. Push to your fork and submit a pull request
  7. Pat yourself on the back and wait for your pull request to be reviewed and merged.

Container based developer flow

If you don't want to maintain a Node developer environment that fits this project you can use containerized commands instead of invoking yarn directly.

# format code and build javascript artifacts
docker buildx bake pre-checkin

# validate all code has correctly formatted and built
docker buildx bake validate

# run tests
docker buildx bake test

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

  • Make sure the README.md and any other relevant documentation are kept up-to-date.
  • We try to follow SemVer v2.0.0. Randomly breaking public APIs is not an option.
  • 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