GitLab forks
Chris (121) 472 posts |
Gah – me being stupid. Just got logged out and didn’t notice. |
Jeffrey Lee (213) 6048 posts |
The fork button looks like it’s working for me. And although I wouldn’t put it past GitLab to be doing something silly, there’s no reason why it should block forking of repositories during a code freeze (you’re reading from the source repo, not writing to it!) Are you sure you didn’t miss the button? It’s near the top-right of the page, next to the “Star” button & notification settings bell. |
Chris (121) 472 posts |
Sorry, me being stupid. I’ve submitted the Merge request now, though I noticed that not all the files seem to have made it – the revised Sprites and Templates didn’t get added for some reason. Right, they seem to be there now. Phew! |
Jeffrey Lee (213) 6048 posts |
Since this a merge request, I’d generally go with the approach of amending your current commit to add the missing files. So you’d do either:
Or:
That’ll update your existing commit to contain the missing files (or whatever other changes you might want to make), and then force-push it to the server (a regular push won’t work because you’ve “rewritten history” by amending the old commit) (git-etiquette note: if you were pushing to a branch which other people are using directly, rewriting history and force-pushing is generally inadvisable, because it can make it difficult for other people to pull those changes) |
Jeffrey Lee (213) 6048 posts |
Hmm, I should make a note to wait longer before starting to reply to your git-related questions ;-) Glad you got it sorted! |
Chris (121) 472 posts |
Thanks Jeffrey. I went with the first of those. It looks like all’s in order now, as far as I can see. Noted on the etiquette. Hopefully Maestro is obscure enough that no one else is likely to want to meddle with it :) |