Labels can be used in many ways to help with your process, here are some options you may want to use:
Label type | Description | How used? | Sample values | |
|---|---|---|---|---|
| 1 | Pipeline label | Name of the pipeline in Datical project | Applied automatically by the deployment packager based on the first label of the REF dbDef | main, currentrelease, hotfix |
| 2 | Script label | Original filename of the script that generated the changeset. | Deployment packager applies this automatically to changesets | myscript.sql |
| 3 | Release label | Changes that are part of a particular release | Typically supplied as "label" argument during packaging (labels option) | 1.0.0, release/1.0.1 |
| 4 | Ticket label | Changes that are related to a specific ticket | Typically supplied in a commit message using square brackets "[DVONE-1111]". Multiple labels can be applied at once using a comma separated list "[DVONE-1111, STORY-5]" | dvone-1111, story-5 |
| 5 | Workflow label | Approval / gating workflows in lieu of context | Applied automatically or manually to indicate that changes are approved to move forward. | passed_qa |
| 6 | Changetype label | Allow/prevent certain types of changes from being deployed to certain environments | Done through the metadata.properties "label" attribute set in specific directories | ddl, dml, procedure |
Note: labels are always stored as lowercase