feat: Expose branch.base_ref and branch.ref_type to env variables#1836
Open
Vitor-Avila wants to merge 1 commit into
Open
feat: Expose branch.base_ref and branch.ref_type to env variables#1836Vitor-Avila wants to merge 1 commit into
Vitor-Avila wants to merge 1 commit into
Conversation
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.
Summary
Exposing branch's
base_refandref_typeas environment variables that can be used in.agor.ymlfiles.Why / context
This is pretty useful to orchestrate environment deployment through Codespaces with Agor. When you create a new branch in Agor, that branch doesn't yet exist upstream. That said, trying to spin up Codespaces would fail. This feature allows to configure the env to start pointing to the base branch (that exists upstream). For example:
Implementation notes
Might not be super widely adopted, but not a big change either. Just expanding the existing framework.
Validation / test plan
Screenshots / demos
No meaningful UI changes.
Risks / rollout / rollback
No risks.
Out of scope / follow-ups
Thought about using the
{{custom.*}}branch properties. It doesn't have a native UI editor, so you must go through MCP change. Also feels like a natural feature.