Skip to content

Compliance updates#398

Merged
cdmren merged 2 commits into
mainfrom
rename-example-to-ci
Jun 23, 2026
Merged

Compliance updates#398
cdmren merged 2 commits into
mainfrom
rename-example-to-ci

Conversation

@cdmren

@cdmren cdmren commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Renames the existing example.yml workflow to ci.yml to satisfy the repository compliance requirement for a "ci" workflow

Mergeabot workflow taken from automated PR #396

Satisfies the requirement for a "ci" workflow without adding
unnecessary Node.js build steps to this composite action repo.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@cdmren cdmren requested a review from a team as a code owner June 22, 2026 23:30
@cdmren cdmren requested review from pbrisbin and removed request for a team June 22, 2026 23:30
@cdmren cdmren changed the title Rename example.yml to ci.yml Compliance updates Jun 22, 2026
@cdmren cdmren requested a review from joris974 June 22, 2026 23:33
@cdmren cdmren enabled auto-merge (squash) June 22, 2026 23:34
@cdmren cdmren merged commit 2b2531d into main Jun 23, 2026
4 checks passed
@cdmren cdmren deleted the rename-example-to-ci branch June 23, 2026 14:54
@pbrisbin

Copy link
Copy Markdown
Member

I had ignored that rule with the justification that example.yml was just as important a convention in actions.

https://github.com/freckle/github-repo-health/pull/326

I was however fighting with github-repo-health not respecting ignores, so I was waiting to see if it still continued to try and create a ci.yml even with this. Did you find that happen somewhere?

@cdmren

cdmren commented Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

I was however fighting with github-repo-health not respecting ignores, so I was waiting to see if it still continued to try and create a ci.yml even with this. Did you find that happen somewhere?

I am not sure what you mean by this (so probably the answer is no).

@pbrisbin

Copy link
Copy Markdown
Member

I'm just guessing you saw our automation create a ci.yml in a PR somewhere, which is what prompted you to do this.

My ignore change should've prevented that by now, but there is a bug in behavior of github-repo-health.

I eventually did track it down, so I'll be fixing it now. I don't know that it's worth reverting this once the ignores are working again, but we could.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants