Skip to content

Commit b29fcad

Browse files
committed
warn branch issue must be resolved in a Codespace
1 parent bb6b1c5 commit b29fcad

1 file changed

Lines changed: 8 additions & 2 deletions

File tree

source/ch-collaboration.ptx

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -173,12 +173,18 @@ Unfortunately, there's no button to push that will fix a commit
173173
made to the local copy of <c>main</c> accidentally, but there
174174
is a quick-enough fix nonetheless.
175175
</p>
176+
<warning>
177+
<p>
178+
This fix must be done in a Codespace,
179+
not GitHub.dev.
180+
</p>
181+
</warning>
176182
<note>
177183
<p>
178184
With branch protection <xref ref="note-branch-protection"/> enabled,
179185
if you accidentally make updates directly to your personal <c>main</c>
180186
branch, attempting to push these from a Codespace will result in
181-
tthe error message <c>Can't push refs to remote.
187+
the error message <c>Can't push refs to remote.
182188
Try running "Pull" first to integrate your changes.</c>
183189
</p>
184190
<p>
@@ -235,7 +241,7 @@ shared branches.
235241
</definition>
236242
<p>
237243
Managing contributions from forked repositories is done using the
238-
same workflow as I recomend for collaborating with trusted colleagues
244+
same workflow as we recommend for collaborating with trusted colleagues
239245
that you've given write access to your repository
240246
(<xref ref="sec-collaborators-prs"/>). The only difference
241247
is that an outside collaborator is creating branches and making commits

0 commit comments

Comments
 (0)