You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As identified in issue #104, this action currently uses the GITHUB_REF_NAME variable for a flexible feature, which covers various GitHub references such as branches or tags. However, GitHub has recently introduced its own usage of GITHUB_REF_NAME for a similar, but not identical, purpose.
To avoid potential conflicts, we will rename the GITHUB_REF_NAME environment variable in this action. This update will be a breaking change and will be introduced in the upcoming v5 release series.
Here are some proposed new names:
CURRENT_REF: A general term that continues to accommodate both branches and tags.
GITHUB_REF_POINT: To highlight that it refers to a specific reference point (not a commit) within GitHub.
The text was updated successfully, but these errors were encountered:
Note
As identified in issue #104, this action currently uses the GITHUB_REF_NAME variable for a flexible feature, which covers various GitHub references such as branches or tags. However, GitHub has recently introduced its own usage of GITHUB_REF_NAME for a similar, but not identical, purpose.
To avoid potential conflicts, we will rename the GITHUB_REF_NAME environment variable in this action. This update will be a breaking change and will be introduced in the upcoming v5 release series.
Here are some proposed new names:
The text was updated successfully, but these errors were encountered: