Skip to content

feat(deploy): Allow setting remote for trigger:dot-release script#20596

Open
LZoog wants to merge 1 commit into
mainfrom
trigger-script-remote-option
Open

feat(deploy): Allow setting remote for trigger:dot-release script#20596
LZoog wants to merge 1 commit into
mainfrom
trigger-script-remote-option

Conversation

@LZoog
Copy link
Copy Markdown
Contributor

@LZoog LZoog commented May 13, 2026

Because:

  • The script assumes mozilla/fxa is set to 'origin'

This commit:

  • Allows passing FXA_REMOTE= to specify a different origin

note to self: update confluence docs when this lands

Copilot AI review requested due to automatic review settings May 13, 2026 22:22
@LZoog LZoog requested a review from a team as a code owner May 13, 2026 22:22
@LZoog LZoog changed the title feat(script): Allow setting remote for trigger:dot-release script feat(deploy): Allow setting remote for trigger:dot-release script May 13, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the dot-release tagging script so it no longer assumes the origin remote, enabling release tagging/pushing against an alternate Git remote when needed.

Changes:

  • Allow overriding the Git remote used by _scripts/trigger-dot-release.sh via REMOTE, defaulting to origin.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 32 to 36
minor="${BASH_REMATCH[2]}"
branch="train-${minor}"
remote="origin"
remote="${REMOTE:-origin}"

echo "Fetching latest tags from ${remote}..."
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair, will do

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also think there's a small chance someone has REMOTE set to something random in their env, just cause its such a ubiquitous term... So maybe GIT_FXA_REMOTE would be less likely to collide?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair point, will update! Though I think FXA_REMOTE should be OK.

@LZoog LZoog force-pushed the trigger-script-remote-option branch from 79187bb to 56d124c Compare May 13, 2026 22:40
Because:
* The script assumes mozilla/fxa is set to 'origin'

This commit:
* Allows passing FXA_REMOTE= to specify a different remote
@LZoog LZoog force-pushed the trigger-script-remote-option branch from 56d124c to 0fb600e Compare May 13, 2026 22:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants