Uh oh!
There was an error while loading. Please reload this page.
chore: add agent rule to base new branches on upstream/main - #3849
Conversation
Add a workspace-specific agent rule to ensure that new conversations/sessions and branches are always based on the latest upstream code to avoid using outdated code states.
There was a problem hiding this comment.
Code Review
This pull request introduces a new workspace rules file (.agents/rules/workspace.md) to guide agents on setting up their local branches. The feedback highlights a potential issue with setting the upstream tracking branch directly to upstream/main in a fork-and-PR workflow, suggesting the use of --no-track to prevent push permission failures.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Uh oh!
There was an error while loading. Please reload this page.
Add a workspace-specific agent rule and a helper script to ensure new conversations/sessions and branches are based on the latest upstream code and track it safely.
Rename the upstream tracking helper script to setup_triangle_branch.sh to better reflect the triangular Git workflow, and update the workspace rules accordingly.
Rename the upstream tracking helper script to create_triangle_branch.sh to better align with branch creation terminology, and update the workspace rules.
Rename the upstream tracking helper script back to setup_triangle_branch.sh to align with preferred naming, and update the workspace rules.
Add a workspace-specific agent rule to ensure that new conversations/sessions and branches are always based on the latest upstream code to avoid using outdated code states.
This comes about after having several sessions go haywire at the start because they
didn't see the latest changes.