Skip to content

Commit

Permalink
fix release action branch naming
Browse files Browse the repository at this point in the history
  • Loading branch information
rehan-fr committed Dec 10, 2024
1 parent fc126cd commit d615c6f
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions .github/actions/github-actions/release-action/action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ runs:
action_path: action.action,
version: action.version,
release_type: releaseType,
branch_name: `${action.version}-${releaseType}-${action.action.replace('/', '-').replace('\\', '-')}`
branch_name: action.action == '.' ? `${action.version}-${releaseType}-${context.repo.repo}` : `${action.version}-${releaseType}-${action.action.replace('/', '-').replace('\\', '-')}`
};
});
Expand All @@ -141,7 +141,7 @@ runs:
git checkout ${{ inputs.base_branch }}
git pull
git checkout -b $version
git push -u origin $version
git push -u origin "refs/heads/$version"
else
echo "Version branch $version exists remotely, checking out"
git checkout $version
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ At UPSIDER, we have a few internal repositories set up with a monorepo structure

We are looking to add a few more features, such as extra signoff from non-coder, label based check, etc.

<sup><sub>NOTE:
<sup><sub>NOTES:
<sup>(\*1)</sup> There are some other hacks, such as using an empty job with the same name to override the status, but those solutions do not provide the flexible control we are after.</sub></sup>

<!-- == imptr: background / end == -->
Expand Down

0 comments on commit d615c6f

Please sign in to comment.