- Create and push a branch with your new features.
- When ready to publish a new production version, create a Pull Request from fore feature branch to
main. - The title of the pull request must contain a special semver tag:
[semver:<segement>]where<segment>is replaced by one of the following values.
| Increment | Description |
|---|---|
| major | Issue a 1.0.0 incremented release |
| minor | Issue a x.1.0 incremented release |
| patch | Issue a x.x.1 incremented release |
| skip | Do not issue a release |
Example: [semver:major]
- Squash and merge. Ensure the semver tag is preserved and entered as a part of the commit message.
- On merge, after manual approval, the orb will automatically be published to the Orb Registry.
Push your branch and CI will trigger dev published version of orb with the commit hash as the version.
To manually pack your orb.yml, you can run circleci orb pack . > orb.yml at the @orb.yml level.
cd src
circleci orb pack . > orb.yml
circleci orb publish orb.yml coda/utils@dev:<your_branch_name>
Using bats to test bash scripts under src/tests.
Individually testing for each command is done in config.yml.
- infra
- headless-chrome
- coda