**Note**: The Component versioning where major versions are automatically resolved ONLY works if your components are in a project explicitly set as a CI/CD Catalog, AND only after a release has been created since enabling this setting.
**Note**: The Component versioning where major versions are automatically resolved ONLY works if your components are in a project explicitly set as a CI/CD Catalog, AND only after a release has been created since enabling this setting.
# Auto DevOps
# Auto DevOps
There is a feature to provide a group default `.gitlab-ci.yml` if none is provided in a project. We may consider doing this at some point.
I thought this simply provided a group default `.gitlab-ci.yml` if none is provided in a project, but upon closer inspection that isn't what this does (I think). Auto DevOps appears to apply GitLab generic workflows based on detected content in your repo. Doesn't appear to be working, at least not well. Could investigate later.
# Trigger Rules
# Trigger Rules
By default if you don't define any rules your job will run on any push. One tricky scenario to be aware of is trying to avoid triggering a CI job when a push contains a change to only the README, CHANGELOG, Screenshot, or similar file. You might think this would work, but it doesn't:
By default if you don't define any rules your job will run on any push. One tricky scenario to be aware of is trying to avoid triggering a CI job when a push contains a change to only the README, CHANGELOG, Screenshot, or similar file. You might think this would work, but it doesn't:
