Replies: 1 comment 1 reply
-
Normally you create and push to a new branch on the repository (if you own the repository) then you do the rest on the github website itself like its explained in this video: https://www.youtube.com/watch?v=jRLGobWwA3Y , I never did it myself but here I think you should first fork the repository and push to it then you should be able to choose the fork on the pull request form, there are some guidelines specific to micropython that must be followed in the docs: https://github.com/micropython/micropython/wiki/ContributorGuidelines |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi
for a project of mine I fixed the dep sleep pin wakeup (using gpio pins) for the esp32-c3 platform and also added the capability to return the source pin of the wakeup. I took inspiration and some of the code from PR 7990 and PR 13333 and merged all using the latest master code as per last friday (the two PRs were based on rather old code).
I know how to program and create my own version of micropython but I never worked with git/github (beyond a "git clone" of the repo) so I am incapable of creating a branch and a pull request (if that is the right way at all) to give back the 4 files I did change for integration into the main codeline.
If someone would like to share some instructions / pointers on how to do that in this repo I would be happy to contribute back.
Beta Was this translation helpful? Give feedback.
All reactions