v0.15.0

Update github output syntax @max-lobur (#48)

what

Update github output syntax

why

Following github docs

references

https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

v0.14.0

• No changes

v0.13.0

• No changes

v0.12.0

Update action.yml

v0.11.0

• No changes

v0.10.0

• No changes

v0.9.0

Fix condition error @goruha (#47)

what

• Fix condition

why

• To solve the error

references

• https://github.com/cloudposse/.github/runs/7776854091?check_suite_focus=true#step:1:62

v0.8.0

Add auto-context functionality @dylanbannon (#43)

what

• Roll entire functionality of cloudposse/github-action-terraform-auto-context action into this repo as a new function to invoke
• Extract all git config from individual scripts into top-level GHA step
• Customizing PR body and commit message according to which function is run
• Reorganizing folder structure
• Labels are not set independently, according to which function is being invoked
• All functions have automated pr and all but context have no-release

why

• Rolling the auto-context functionality into this repo makes maintaining all the GHAs easier, and it logically fits in here.
• All the reorganizations just make the action as a whole more maintainable.
• Generally, this makes the existing function paradigm of auto-format more extensible
• With the current label configuration, though, we can prevent PRs that don't affect functionality from generating a release (relying on cloudposse/github-action-auto-release's feature of not releasing when the no-release label is attached to a PR).

references

• cloudposse/github-action-terraform-auto-context
• cloudposse/github-action-auto-release
• CPCO-600
• CPCO-441

v0.7.0

allowing auto-format action to run from branches @dylanbannon (#45)

what

• Changing pull_request_target trigger to pull_request

why

• This will allow testing actions on branches before merging them

updating branch pin from the defunct review-branch branch to the main branch @dylanbannon (#44)

what

• Title says it all. This was overlooked when merging from review-branch previously.

why

• Currently, the action tries on a branch that doesn't exist. Now, it might work.

v0.6.0

• No changes