Open up commits?

[mdecourcy]

Hi there, I was having issues with the NWS_Alerts tab. Wanted to commit and create a PR with my changes but was met with a 403 forbidden. Thanks for providing this integration!

[finity69x2]

I'm not sure what you mean but you can open a PR if you want.

you just can't commit the changes yourself.

what is the issue you are having?

[mdecourcy]

Might just be an issue with my locally saved creds on this machine, I'll check after I wrap up at work

[jarrodsfarrell]

@mdecourcy You're trying to push directly to someone else's repo you do not have access to. You have to fork, clone your fork, branch, commit, push, then PR.

The flow I use to committing and PRing to someone else's project is the following:

• Through GitHub web, you fork the repo. This makes a personal copy for yourself.
• You clone your fork.
• Create a new branch from main/master or some other branch of interest.
• Make your commits
• Push
• Visit your repo and you should get a yellow banner indicating you can PR your changes.

This is my flow, but I know there's quicker ways via GitHub's CLI and different ways to begin a PR. Explore around.

You will occasionally have to update your fork and there's a way to do it on the web, but typically I set up another remote on my local repo—like upstream—, switch to your fork's main, git fetch upstream, git merge upstream/main or something of that effect then git push. Ideally it should fast-forward, but if it does something else or fails then the owner did a force push that broke the history or you have local commits that are conflicting.

[mdecourcy]

Ah I see, my mistake! First attempt at open source contributions. I'm used to just feature branching and PRing at work. I'll fork and make a PR now.

[jarrodsfarrell]

@mdecourcy No problem, and that would be a valid way to do a PR as well on repos you have access to as well.