Commit 76466fe5 authored by Peter Leitzen's avatar Peter Leitzen

Merge branch 'pl-gitlab-ci-changelogs-yml' into 'master'

CI: No need to track changelogs/**/*.yml anymore

See merge request gitlab-org/gitlab!69757
parents c63253ad 0d83b3b8
......@@ -142,7 +142,6 @@
- ".gitlab-ci.yml"
- ".gitlab/ci/**/*.yml"
- "lib/gitlab/ci/templates/**/*.yml"
- "{,ee/,jh/}changelogs/**/*.yml"
.docs-patterns: &docs-patterns
- ".gitlab/route-map.yml"
......
# Yamllint of CI-related yaml and changelogs.
# Yamllint of CI-related yaml.
# This uses rules from project root `.yamllint`.
lint-yaml:
extends:
......@@ -8,6 +8,6 @@ lint-yaml:
stage: test
needs: []
variables:
LINT_PATHS: .gitlab-ci.yml .gitlab/ci lib/gitlab/ci/templates changelogs
LINT_PATHS: .gitlab-ci.yml .gitlab/ci lib/gitlab/ci/templates
script:
- yamllint -f colored $LINT_PATHS
# Generating changelog entries
To generate and validate your changelog entries:
From GitLab 14.0.0 onwards, [CHANGELOG.md](../CHANGELOG.md) is generated
by parsing [Git trailers](https://git-scm.com/docs/git-interpret-trailers)
in commit messages.
1. Run `bin/changelog` to generate.
1. Run `yamllint changelogs` to validate.
See [development/changelog] documentation for detailed usage.
[development/changelog]: https://docs.gitlab.com/ee/development/changelog.html
See [documentation](https://docs.gitlab.com/ee/development/changelog.html#how-to-generate-a-changelog-entry)
on how to generate changelog entries.
# Changelog archival
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment