Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Update release configuration files to correctly use conventional-commits #44

Conversation

bryantbiggs
Copy link
Member

Description

  • Update .releaserc.json to ensure conventional-commit standards are used by semantic-releaser
  • Update .pre-commit-config.yaml versions to latest and ensure end-of-file-fixer hook is used
  • Add pr-title.yml GitHub workflow for ensuring PR titles follow conventional-commit standards
  • Fix release.yml GitHub workflow to ensure release process does not run on forks; ref Update release workflow to only run on source repos meta#25
  • Add stale-actions.yaml to ensure issues and pull requests are routinely cleaned up; copie from EKS repository

Motivation and Context

  • Ensure organization configurations are aligned and standardized; most of these changes are copied from the current EKS repository

Breaking Changes

  • No

How Has This Been Tested?

  • CI checks only

…al-commits

- Update `.releaserc.json` to ensure conventional-commit standards are used by semantic-releaser
- Update `.pre-commit-config.yaml` versions to latest and ensure `end-of-file-fixer` hook is used
- Add `pr-title.yml` GitHub workflow for ensuring PR titles follow conventional-commit standards
- Fix `release.yml` GitHub workflow to ensure release process does not run on forks; ref terraform-aws-modules/meta#25
- Add `stale-actions.yaml` to ensure issues and pull requests are routinely cleaned up; copied from EKS repository
@antonbabenko antonbabenko merged commit 8c2b624 into terraform-aws-modules:master Jan 10, 2022
@antonbabenko
Copy link
Member

This PR is included in version 3.0.1 🎉

@bryantbiggs bryantbiggs deleted the chore/update-release-configs branch January 10, 2022 12:40
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants