Contributing to Dagger
The best way to find a good contribution is to use Dagger for something. Then write down what problems you encounter. Could be as simple as a question you had, that the docs didn't answer. Or a bug in the tool, or a missing CUE package. Then pick an item that you're comfortable with in terms of difficulty, and give it a try. 🙂
You can ask questions along the way, we're always happy to help you with your contribution. The bigger the contribution, the earlier you should talk to maintainers to make sure you're taking the right approach and are not wasting your effort on something that will not get merged.
Package Style Guide
If you're contributing CUE packages, be sure to follow the Package Coding Style guide as well.
The recommended workflow is to fork the repository and open pull requests from your fork.
1. Fork, clone & configure Dagger upstream
- Click on the Fork button on GitHub
- Clone your fork
- Add the upstream repository as a new remote
# Clone repository
git clone https://github.com/$YOUR_GITHUB_USER/$REPOSITORY.git
# Add upstream origin
git remote add upstream firstname.lastname@example.org:dagger/$REPOSITORY.git
2. Create a pull request
# Create a new feature branch
git checkout -b my_feature_branch
# Make changes to your branch
# Commit changes - remember to sign!
git commit -s
# Push your new feature branch
git push my_feature_branch
# Create a new pull request from https://github.com/dagger/$REPOSITORY
3. Update your pull request with latest changes
# Checkout main branch
git checkout main
# Update your fork's main branch from upstream
git pull upstream main
# Checkout your feature branch
git checkout my_feature_branch
# Rebase your feature branch changes on top of the updated main branch
git rebase main
# Update your pull request with latest changes
git push -f my_feature_branch
Scope of pull requests
We prefer small incremental changes that can be reviewed and merged quickly. It's OK if it takes multiple pull requests to close an issue.
The idea is that each improvement should land in Dagger's main branch within a few hours. The sooner we can get multiple people looking at and agreeing on a specific change, the quicker we will have it out in a release. The quicker we can get these small improvementes in a Dagger release, the quicker we can get feedback from our users and find out what doesn't work, or what we have missed.
The added benefit is that this will force everyone to think about handling partially implemented features & non-breaking changes. Both are great approaches, and they work really well in the context of Dagger.
"Small incremental changes ftw" -> Small pull requests that get merged within hours!
Contributions to this project must be accompanied by a Developer Certificate of Origin (DCO).
All commit messages must contain the Signed-off-by line with an email address
that matches the commit author. When commiting, use the
git commit -s
The Signed-off-by line must match the author's real name, otherwise the PR will be rejected.
- Group Commits: Each commit should represent a meaningful change (e.g. implement feature X, fix bug Y, ...).
- For instance, a PR should not look like 1) Add Feature X 2) Fix Typo 3) Changes to features X 5) Bugfix for feature X 6) Fix Linter 7) ...
- Instead, these commits should be squashed together into a single "Add Feature" commit.
- Each commit should work on its own: it must compile, pass the linter and so on.
- This makes life much easier when using
git bisect, etc.
- For instance, when doing a
git blameon a file to figure out why a change was introduced, it's pretty meaningless to see a Fix linter commit message. "Add Feature X" is much more meaningful.
- This makes life much easier when using
git rebase -i mainto group commits together and rewrite their commit message.
- To add changes to the previous commit, use
git commit --amend -s. This will change the last commit (amend) instead of creating a new commit.
- Format: Use the imperative mood in the subject line: "If applied, this commit will your subject line here"
- Add the following prefixes to your commit message to help trigger automated processes1:
docs:for documentation changes only (e.g.,
docs: Fix typo in X);
test:for changes to tests only (e.g.,
test: Check if X does Y);
chore:general things that should be excluded (e.g.,
chore: Clean up X);
website:for the documentation website (i.e., the frontend code; e.g.,
website: Add X link to navbar);
ci:for internal CI specific changes (e.g.,
ci: Enable X for tests);
infra:for infrastructure changes (e.g.,
infra: Enable cloudfront for X);
fix: for improvements and bugfixes that do not introduce a feature (e.g.,
fix: improve error message);
feat: for new features (e.g.,
feat: implement --cache-to feature to export cache)
Use relative file paths for links
Instead of using URLs to link to a doc page, use relative file paths instead:
❌ This is [a problematic link](/doc-url).
✅ This is [a good link](../relative-doc-file-path.md).
The docs compiler will replace file links with URLs automatically. This helps prevent broken internal links. If a file gets renamed, the compiler will catch broken links and throw an error. Learn more.
How to run linters locally?
# From the repository root, run all linters:
dagger do lint
# Only run a specific linter:
dagger do lint markdown
# Look inside the ci.cue file to see all available linters
How to re-run all GitHub Actions jobs?
There isn't a button that Dagger contributors can click in their fork that will re-run all GitHub Actions jobs. See issue #1169 for more context.
The current workaround is to re-create the last commit:
git commit --amend -s
# Force push the new commit to re-run all GitHub Actions jobs:
git push -f mybranch
Can I use a remote development environment?
Yes! The Dagger repository has Github Codespaces configuration included to help you get started contributing directly from GitHub.
The versions of
cue you are working against will be pre-installed so you can develop your packages, plans and tests with the right tools.
You will also have basic syntax highlighting and formatting for CUE in Visual Studio Code via pre-installed extensions.
Support for other platforms, such as Gitpod, may be added if there is demand. Visit the developer experience discussion on GitHub to show your interest.
How can I add a new secret for integration tests?
1/4. Ensure that you have SOPS installed.
2/4. Run the following from the top-level of your local repository fork:
# Add a new secret with the correct value
# Use one of the existing ones as an example
3/4. Save the
4/4. Commit and push the changes.
Please note that anyone will be able to read all secrets stored in
tests/secrets_sops.yaml by following the steps above.