Benjamin K.
Benjamin K.
Should work out of the box imo. Are you working on a public repo where I could have a look at?
I followed the suggestion of @julian7 and it works. I included old CHANGELOG entries but let git-chglog generate the bottom part because I made it in the same style before....
I proposed the changes in another PR. Ready for review
> There are a couple of parameters missing from edit_protection > > required_linear_history allow_force_pushes allow_deletions block_creations required_conversation_resolution > > This is from https://docs.github.com/en/rest/branches/branch-protection#update-branch-protection https://github.com/PyGithub/PyGithub/pull/2512 writes `required_conversation_resolution`, I linked a PR...
same as in #2473: if we don't want to add the .pyi files back this PR should be closed in my opinion to clean up a little bit. @trim21 @EnricoMi
I had that trouble as well. For reference: One needs to replace the string **two times** in the recorded file - at upper and lower position.
I only got it running with `--auth_with_token`, thought that is needed die to 2 factor authentication. Is this not correct and I could recors in another way?
> Could you say a `Commit` is the Github commit (as in the Github concept of a commit) and a `GitCommit` is the Git commit (as in the Git concept...
updated the documentation and added the new URL's. Ready to review @EnricoMi
@austinsasko seams you have to integrate the latest changes from main into your branch. Also some review comments are waiting to be integrated. Would be nice to see further progress...