Skip to content

Conversation

@henrymercer
Copy link
Contributor

The Action requires GHES 3.3, so we can safely remove this fallback logic for GHES 2.22 and GHES 3.0.

Merge / deployment checklist

  • Confirm this change is backwards compatible with existing workflows.
  • Confirm the readme has been updated if necessary.
  • Confirm the changelog has been updated if necessary.

@henrymercer henrymercer requested a review from a team as a code owner November 23, 2022 14:04
Copy link
Contributor

@aeisenberg aeisenberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aeisenberg
Copy link
Contributor

Otherwise looks reasonable.

@henrymercer henrymercer force-pushed the henrymercer/remove-dead-code branch from d8597f3 to bc341c5 Compare November 23, 2022 18:19
@henrymercer
Copy link
Contributor Author

So GITHUB_ACTION_REPOSITORY is only set when calling an Action from another repository. We still need to populate it manually if we're running locally.

I've updated the PR to only remove the code that deals with the fact that GHES 2.22 didn't populate GITHUB_ACTION_REPOSITORY even when the Action is called from anothe repository.

Copy link
Contributor

@aeisenberg aeisenberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM assuming all jobs pass.

@henrymercer henrymercer merged commit 187515b into main Nov 23, 2022
@henrymercer henrymercer deleted the henrymercer/remove-dead-code branch November 23, 2022 18:55
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