CI: Reference workflow file name for old branch

[cryos]

Description

Switch to use the workflow file name as the name is getting missed in the merged code in main. Verified the behavior locally too. This is a follow up from #555 addressing an issue seen after merging.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[copy-pr-bot]

Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[cryos]

/ok to test

[cryos]

@leofang see failures after merge where the workflow name is not found. In general I have used workflow file names and they have been reliable.

[leofang]

Thanks, Marcus! Yes, I noticed the main failed too. So instead of backporting the CI name change, we just fix it by referring to the workflow filename. (I did not know this works!) The only catch is that when the current main branch becomes the backport branch in the future, we'll need to change it to ci.yaml.

[leofang]

One question: Why didn't we observe this failure in #555?

[cryos]

One question: Why didn't we observe this failure in #555?

Not clear and that is frustrating! I guess we hit a corner case, I will merge this and see if it is more reliable.

[cryos]

Thanks, Marcus! Yes, I noticed the main failed too. So instead of backporting the CI name change, we just fix it by referring to the workflow filename. (I did not know this works!) The only catch is that when the current main branch becomes the backport branch in the future, we'll need to change it to ci.yaml.

Yes, and I think I will have factored out some of this common code into helper scripts better by that point too.

[github-actions]

Doc Preview CI
Preview removed because the pull request was closed or merged.