Skip to content
This repository has been archived by the owner on May 28, 2024. It is now read-only.

Clarify SCM and release requirements #218

Merged
merged 2 commits into from
Oct 26, 2022
Merged

Clarify SCM and release requirements #218

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
410559d
Require git repos
mariolenz Oct 13, 2022
051db8e
Clarify tagging and releasing
mariolenz Oct 15, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion collection_checklist.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Note for reviewers: If you don't know how to check any of the points below, plea
- [ ] has a policy of releasing, versioning and deprecation announced to contributors and users in some way
- [ ] have a Code of Conduct (CoC) compatible with the [Ansible Code of Conduct (CoC)](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html)
- [ ] have a publicly available issue tracker that does not require a paid level of service to create an account or view issues
- [ ] have a public SCM repository, releases of the collection are tagged in this repository
- [ ] have a public git repository, releases of the collection are tagged in this repository

**Standards and documentation:**
- [ ] adheres to [semantic versioning](https://semver.org/)
Expand Down
4 changes: 3 additions & 1 deletion collection_requirements.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -280,7 +280,9 @@ licensing and legal concerns that may otherwise affect your code.
Repository management
=====================

Every collection MUST have a public SCM repository and releases of the collection MUST be tagged in this repository.
Every collection MUST have a public git repository and releases of the collection MUST be tagged in this repository.

We are open to add more SCMs once our tooling supports them.
mariolenz marked this conversation as resolved.
Show resolved Hide resolved

Branch name and configuration
-----------------------------
Expand Down