Draft
Fix workflows: remove reference to non-existent set_environment job and add staging support#76
Conversation
Co-authored-by: ronaldtse <11865+ronaldtse@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix code for build_deploy workflow
Fix workflows: remove reference to non-existent set_environment job
Nov 11, 2025
Contributor
|
@copilot continue fixing |
Co-authored-by: ronaldtse <11865+ronaldtse@users.noreply.github.com>
Author
Completed the fix. Added staging branch trigger to build_deploy workflow in commit 3f06ece. The workflow now:
Both workflows are now consistent and match the documented behavior in README. |
Copilot
AI
changed the title
Fix workflows: remove reference to non-existent set_environment job
Fix workflows: remove reference to non-existent set_environment job and add staging support
Nov 11, 2025
Contributor
|
@copilot fix the remaining issues for deployment |
Co-authored-by: ronaldtse <11865+ronaldtse@users.noreply.github.com>
Author
Fixed deployment environment configuration in commit 791bf42. Both workflows now use conditional environments based on the branch:
This allows GitHub environment protection rules and configurations to work correctly for each deployment target. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both
build_deploy.ymlandcheck_links.ymlreferenceneeds.set_environment.outputs.data_branchbut noset_environmentjob exists, causing workflow failures. Additionally,build_deploy.ymlwas missing the staging branch trigger and both workflows had hardcoded environment configurations.Changes
needs.set_environment.outputs.data_branchwith conditional expression based ongithub.refrefs/heads/staging→stagingbranch, defaults tomainfor all other refsbuild_deploy.ymlandcheck_links.ymlworkflowsstagingto trigger branches inbuild_deploy.ymlto matchcheck_links.ymlThis aligns with the documented behavior where production deploys from
itu-ob-data@maintohttps://www.ituob.organd staging deploys fromitu-ob-data@stagingtohttps://staging-www.ituob.org. Both workflows now trigger on both main and staging branches and use the appropriate GitHub environment configuration for each deployment target.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.