Check fail in STM32Cube 'challenge' project #95
-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
Hey! I've found the issue. I've already implemented a fix, but I'll test it tonight to make sure it works. In the meantime, could you please create the corresponding issue in this repo so I can link it to the fix? Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I've tested the patch and all tests are passing. I'm waiting for you to create the issue so I can link it to the fix and push it. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hey! I've pushed the patch. To incorporate it into your repo, run the following commands: git switch main
git pull
git remote add upstream-2 https://github.com/TheAlbertDev/masb-course-timers.git
git fetch upstream-2
git cherry-pick cfd06da
git push
git switch stm32cube-challenge
git rebase main
git push --forceHere's what each command does: 1. Get your git switch main
git pullSwitch to your 2. Add the course repo as a second remote and fetch it git remote add upstream-2 https://github.com/TheAlbertDev/masb-course-timers.git
git fetch upstream-2This registers the course repo as a new remote called 3. Cherry-pick the patch commit git cherry-pick cfd06daThis takes the specific commit with the fix ( gitGraph
commit id: "..."
commit id: "your last commit"
commit id: "cfd06da (patch)" type: HIGHLIGHT
4. Push git pushPush your updated 5. Rebase your working branch on top of the updated git switch stm32cube-challenge
git rebase main
git push --forceSwitch to your working branch ( gitGraph
commit id: "..."
commit id: "your last commit"
commit id: "cfd06da (patch)" type: HIGHLIGHT
branch stm32cube-challenge
commit id: "your work (rebased)"
Let me know if you run into any issues! 💪 |
Beta Was this translation helpful? Give feedback.



Hey! I've pushed the patch. To incorporate it into your repo, run the following commands:
Here's what each command does:
1. Get your
mainbranch up to dateSwitch to your
mainbranch and pull the latest changes from your remote.2. Add the course repo as a second remote and fetch it
This registers the course repo as a new remote called
upstream-2…