Will branches and PR style workflows work?

Platform
1

I’m looking to implement stages in a more structured manner using branches and PR. Would this work with the current git setup for the challenges?

3

Hey @OlaoluwaM, we don’t currently support PR-based workflows, but using branches should work fine. Let me know if you run into any issues.

4

What if I merge to main on my personal clone then pull and do a submit?

5

Sounds like it should work. One caveat: the tester only monitors the master branch, not main.

6

Right, yes I meant master. Could this break the sync functionality? I think there’d be a lot more flexibility if y’all would release a GitHub action that people could use to run tests and advance their progress that way people can do whatever they want with their repos and stuff

7

Could this break the sync functionality?

It depends on what exactly you’re planning to do.

Note that the sync to GitHub is one-directional: commits to our server are synced to GitHub, and will overwrite changes there. So I’d recommend avoiding using GitHub as the primary workflow.

I think there’d be a lot more flexibility if y’all would release a GitHub action that people could use to run tests and advance their progress that way people can do whatever they want with their repos and stuff

That’s a great suggestion! We explored something along those lines in the past, but the added delay made it difficult to deliver a smooth experience. It’s something we’d still like to revisit in the future though.

8

Can I just undo the sync and push separately?

9

Yep, and here’s how to stop the syncing:

image
image554×906 50.3 KB

image
image1174×1398 64.7 KB

10

Yep! And I add I can add the codecrafter repo as a separate remote using the information I get from the “Copy Github Repository URL” button, yes?

11

How does the CLI work with respect to the git remotes? Does the codecrafters remote need to be the origin? Or can it be something else? Is the CLI ok so long as there is a remote url pointing to the codecrafters repo? Here is how I have it right now:

[Edited by Andy to remove the screenshot]

12

IIRC, the CodeCrafters remote does not have to be named origin. Looks like your current setup should work. Let me know if you run into any issues.

1 Like
13

Question, does the default branch need to be called master? Can it be renamed? Will the submit script be ok with that?

14

Yes, currently we only monitor the master branch, so renaming the default branch would prevent tests from being triggered.