v0.4.0

Specify config for auto-release @osterman (#19)

what

• Use .github/auto-release.yml instead of .github/configs/auto-release.yml

why

• The upstream action changed it's path to configs/draft-release.yml
• Our configs in 99% our repos use auto-release.yml
• Since we can't move 99% of the locations of configs like settings.yml or mergify.yml, introducing a configs/ folder only makes configs more disbursed

Undo last attempt at fixing checkout @osterman (#18)

what

• Remove flags that caused error

  fatal: could not read Username for 'https://github.com': No such device or address

why

• Using --force-with-lease should probably all that's needed to get this to work

relates to

• stefanzweifel/git-auto-commit-action#2

Force push readme @osterman (#17)

what

• Force push new readme
• Add missing issue templates
• Fix broken URL

why

• Force pushing is required for pushing to protected branches with bypass permission

Checkout Repo @osterman (#16)

what

• checkout repo

why

• readme action expects repo to be checked out

remove auto-readme workflow and move to scheduled workflow @osterman (#15)

what

• move auto-readme functionality into scheduled workflow
• use readme action
• fix org ref

why

• DRY

Test using readme action @osterman (#14)

what

• Rip out the previous implementation and replace with readme action
• Remove repo-banner workflow which is now handled by the readme action
• Always rebuild readme and do so in the security context so we can push to main

why

• READMEs out of date is the most common issue preventing releases
• No reason we cannot just always generate it

Cut releases when workflows change @osterman (#13)

what

• Adjust the conditions for cutting a release to include changes to .github

why

• We'll be pinning to releases of this configuration repository

Use auto commit action and github app in release environment @osterman (#12)

what

• Use a GitHub App to update the README so we can push to a protected branch
• Use protected branch so we can auto-merge with Mergify

why

• Fix automated releases

Create repo scaffolding @osterman (#11)

what

• Implement a github action used by the organization to manage scaffolding
• Run make all for a given repository type
• Add a workflow to test the scheduled runs

why

• Manage repos at scale

Update the readme template @osterman (#10)

what

• Fix references to GitHub Actions

why

• Copied from our default template that applied more to terraform modules

fix github-actions bot @osterman (#9)

what

• The github-actions app should be referred to as github-actions[bot]

why

• For auto-merging rules

Fix mergify settings @osterman (#8)

what

• Use yaml anchors
• Treat github-actions as a bot

why

• This hopefully fixes merging

v0.3.0

Add mergable config @osterman (#7)

what

• Use this repo as the organization's config for mergable
• Auto-merge readme/image updates

why

• Automate repo maintenance

v0.2.0

Add community files @osterman (#5)

what

• Add community files

why

• Needed for open source support of organization

0.1.0: More Release Fixes (#4)

* rebuild readme JOB_SUMMARY

* pass GITHUB_TOKEN