-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JIRA labels for DEPLOY_BEFORE_MERGE = true #924
Comments
@0ptaq0 that should be hard to implement :) Time for your first PR to sfdx-hardis ? 😇 The code building the tag is here ->
You can add a condition using isDeployBefore merge To get the targetBranch, you can use const prInfo = await GitProvider.getPullRequestInfo();
const targetBranch = prInfo?.targetBranch || process.env.FORCE_TARGET_BRANCH |
Hi @nvuillam, This is my first TS code so I have no idea what I am doing, but I managed to make some changes locally on a feature branch.
Can you please give me permission to push? |
Hi @nvuillam, just a reminder, how should I add the PR? |
@0ptaq0 sorry for the delay :) You need to fork the repo |
@0ptaq0 and not the last I hope ! :) Going to check your PR :) |
…true (#924) (#960) * using target branch for jira labels when deploy before merge flag is true (#924) * updated changelog with jira labels changes (#924) * Update CHANGELOG.md * Update package.json --------- Co-authored-by: Nicolas Vuillamy <[email protected]>
Some time ago a great feature was introduced to support my exotic way of deployment: SFDX_HARDIS_DEPLOY_BEFORE_MERGE: "true"
Thank you for that!
When we have a pull/merge request, the merge results (diff) are deployed to the target branch, and if that succeeded the pull/merge request is merged.
I am using that approach but have one ask for additional support for my "deploy before merge" for jira labels.
If
SFDX_HARDIS_DEPLOY_BEFORE_MERGE: "true"
create a tag in a way:UPPERCASE(target_branch_name) + "_DEPLOYED"
Currently, we do have:
UPPERCASE(branch_name) + "_DEPLOYED"
which is pointing to the source branch od the merge request and is not really accurate in that case.The text was updated successfully, but these errors were encountered: