Skip to content

Releases: cloudposse/.github

v0.2.1

25 Mar 19:42
6fb0ad1
Compare
Choose a tag to compare

🐛 Bug Fixes

Prevent looping on triage label @Nuru (#58) ## what
  • Do not add triage label to PR after it has been removed due to being approved

why

  • Remove infinite loop

references

v0.2.0

19 Mar 22:30
60a00a3
Compare
Choose a tag to compare
Rename shared auto release @goruha (#57) ## what * Rename shared auto release
Set `release` environment for `shared-auto-release` workflow @goruha (#56) ## what * Set `release` environment for `shared-auto-release` workflow

why

  • Reuse existing environment
Auto release fix @goruha (#54) # What * Use auto relesase shared workflow

Why

Update shared-auto-release config name @goruha (#53) ## what * Set `auto-release.yml` as the default config

why

  • Follow existing config names pattern
Added shared auto release workflow @goruha (#51) ## what * Added shared auto-release workflow

why

  • Centralized auto-release workflow

references

Update teams permissions @goruha (#52) ## what * Update teams permissions

why

  • Fix Codeownership verification
Add more conditions for mergify config @osterman (#49) ## what - Check that PR is not a WIP when commenting - Use explict `and` everywhere needed in anchors - Delay 5 minutes since last update before welcoming - Label stale pull requests - Close stale pull requests 3 days after last update - Use active voice - Rename anchors to be more clear - Use more anchors to make it easier to understand what everything means

why

  • Some edge cases we encountered
  • Make mergify less error prone
Fix templates in README.md.gotmpl @osterman (#48) ## what - Pass context to readme template

why

  • Broke recently in #47
display templates depending on available sections @osterman (#47) ## what * Depending on available sections, display specific tips

why

  • Tips can get overwhelming if certain sections are empty
Update README.md.gotmpl @osterman (#45) ## what * Promote CTAs for atmos & our reference architectures * De-emphasize some other CTAs

why

  • It's our core offering
Add missing migration label @osterman (#44) ## what * Add `migration` label * Disable `mergeable` condition as it needs to better communicate why something is not mergable

why

  • It will be used to label PRs that perform repo migrations
Implement migrations and initial versions of settings.yml and mergify.yml @osterman (#43) ## what - Add `migration/` folder for carrying out github repo migrations - Add `mergify.yml` and `settings.yml`

why

  • Repo automation @ scale
chore(deps): update nick-fields/assert-action action to v2 @renovate (#39) This PR contains the following updates:
Package Type Update Change
nick-fields/assert-action action major v1 -> v2

Release Notes

nick-fields/assert-action (nick-fields/assert-action)

v2

Compare Source


chore(deps): update cloudposse/actions action to v0.33.0 @renovate (#38) This PR contains the following updates:
Package Type Update Change
cloudposse/actions action minor 0.30.0 -> 0.33.0

Release Notes

cloudposse/actions (cloudposse/actions)

v0.33.0

Compare Source

v0.32.0: 0.32.0 Update cloned actions

Compare Source

What's Changed

New Contributors

Full Changelog: cloudposse/actions@0.31.0...0.32.0

v0.31.0: Update Alpine-based actions to Alpine 3.16

Compare Source

What's Changed

Full Changelog: cloudposse/actions@0.30.0...0.31.0


fix: renovate bot complaint #11 @hans-d (#37) ## what *fix offending part in renovatbot config

why

  • closes #11
  • prevents renovabot from maintaining versions
Update node16 actions to node20 versions @Nuru (#36) ## what
  • Update node16 actions to node20 versions
    • actions/checkout -> v4
    • stefanzweifel/git-auto-commit-action -> v5

why

  • Node16 support is deprecated

references

Updates to contrib guidelines @joe-niland (#30) ## what * Information related to contributing to Cloud Posse Terraform modules

why

  • Provide a guide for reviewers and authors

references

  • None
Fix md formatting @osterman (#35) ## what * Add newlines between HTML and markdown

why

  • GitHub markdown engine will treat any text immediately following HTML as HTML. The markdown then doesn't get rendered. Adding a newline in between the HTML and markdown formatted text, restores the markdown rendering behavior.
Ditch reference-style links @osterman (#34) ## what * Convert most markdown links and images to raw HTML

why

  • Many reference-style links stopped working with #33.
  • Most of the README is already in HTML, there's no benefit to sticking with Markdown format
  • README is generated, let's just generate HTML
  • Use gotempate variables as references instead

references

Darkmode @osterman (#33) ## what * Render images for darkmode/lightmode * Improve checkboxes in profile page * Move badges to the right * Reduce some of our boilerplate using details blocks

why

  • Transparent images with black text do not render well in dark mode

references

Optimize Profile Page @osterman (#32) ## what * Move content into `
` block * Add CTAs

why

  • It's too long as it is, hiding our repos.
  • Extends #31
Use Square Badges @osterman (#31) ## what * Use `?style=for-the-badge` rectangular badges * Use the new shield for SweetOps hosted via CloudFlare worker ![Slack](https://slack.cloudposse.com/for-the-badge.svg) * Add CTAs to org profile

why

  • Refresh our look & feel
  • They look more like a CTA

demo

image
Update note ...
Read more

v0.1.0

23 May 19:27
4291c66
Compare
Choose a tag to compare
adding workflows and metadata files for new actions @dylanbannon (#7) ### what Adding a lot of repo bootstrap files, all of which are meant to be copied from the current repository into any other repository by use of the `auto-format.yml` workflow. Also included in the "bootstrap files" designation are the top-level `renovate.json` and `Makefile` files.

Among the bootstrap files are GitHub Actions workflows calling the following GitHub Actions:

See README.md for more details.

why

In addition to its other anointed uses, we intend to use this repo as a distribution point for Cloud Posse's suite of repo bootstrapping files in the near future. At this point, all the desired files are in the repo and their locations in the repo are identical to where they'd likely be placed in any other repo.

git.io->cloudposse.tools update @dylanbannon (#9) ## what and why Change all references to `git.io/build-harness` into `cloudposse.tools/build-harness`, since `git.io` redirects will stop working on April 29th, 2022.

References

  • DEV-143
Add Organizational Profile @osterman (#8) ## what * Adds a GitHub Organizational Profile Page

why

  • Showcase what we do at Cloud Posse
default funding settings @maximmi (#6) ## what * default funding settings
Add pre-commit workflow @3h4x (#4) #what - test pre-commit workflow
Rename terraform workflow files to new convention @3h4x (#3) # what - renaming files for terraform workflow # why - because https://github.com//pull/2 didn't fix the issue described there
Rename terraform workflow to cloudposse terraform workflow @3h4x (#2) # what - renaming of metadata for cloudposse terraform workflow - adding `tf` icon

why

Screenshot 2020-07-23 at 16 50 04 Screenshot 2020-07-23 at 16 49 56
Terraform simple workflow @3h4x (#1) ## What * Add simple terraform workflow to inherit github actions in organization modules

Why

  • To globalize rules for repositories and github actions

References