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
I have the following scenario.
Repository Client is dependent on Repository Core. We are using SemVer to create tags for each of them but we are thinking of adding a build number to the tag name to not increment version for every monitor thing while still in testing environment.
My question would be the following.
If Core Repo would have multiple tags with the same version but different builds would it be possible for checkout action to pull the latest build from a specified version ?
Eg.
Core Tags:
v1.2.3+20230809
v1.2.3+20230810
v1.2.3+20230811
v1.2.4+20230811
Client Dependency:
Core v1.2.3
action/checkout pulls v1.2.3+20230811 (latest based on committed date not necessarily build number)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
I have the following scenario.
Repository Client is dependent on Repository Core. We are using SemVer to create tags for each of them but we are thinking of adding a build number to the tag name to not increment version for every monitor thing while still in testing environment.
My question would be the following.
If Core Repo would have multiple tags with the same version but different builds would it be possible for checkout action to pull the latest build from a specified version ?
Eg.
Core Tags:
Client Dependency:
action/checkout pulls v1.2.3+20230811 (latest based on committed date not necessarily build number)
Right now I am just using the standard:
uses: actions/[email protected]
with:
repository: ${{ env.core_repo }}
ref: ${{ env.core_tag }}
path: 'core'
Beta Was this translation helpful? Give feedback.
All reactions