Hello @Subash Rajaa, you should be forking the osquery repository, commit your work in a separate branch (not master) on your own repository, and then you can open a PR in the upstream repository, which points to your branch.

Thank you so much. I have created a local branch called fflush-consolebuufer-ungraceful-exit

Yes, but you shouldn’t be pushing it on the upstream repository. You have to create a fork of the osquery repository first, you can do that from the github website

ok then push the commit to the forlk ?

yep, and then back on the Github UI on the upstream osquery page, you should see a banner saying that you can open a PR with the branch you pushed to

created a fork. https://github.com/srajaa/osquery

otherwise you can go in the Pull Requests page and use the

New pull request

button, and then click the link that says

compare across forks

. Then you select the branch

and create a commit against it

For right now you don’t need to; if you’ve your code ready, you can add your repo with

git remote add myosquery git@github.com:srajaa/osquery

C:\Source\osquery>git push myosquery1 kex_exchange_identification: read: Connection reset by peer fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

1. Do you have an ssh key configured in your Github profile, that you’re now using to push to you repo? 2. If so, can you please execute

git remote -v

?

1. yes I have a personal access token

I see, if you’re using a PAT, you need to use the https protocol. I think you should be changing the URL to

git remote set-url myosquery1 <https://srajaa>:<token>@github.com/srajaa/osquery

done...thank you so much