You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did not see this warning at the beginning of githubkit/rest/types.py and githubkit/rest/models.py:
"""DO NOT EDIT THIS FILE!
This file is automatically @generated by githubkit using the follow command:
python -m codegen && isort . && black .
See https://github.com/github/rest-api-description for more information.
"""
And that's exactly what I did 😁
Looking a second time at pyproject.toml I think my proposed change is wrong.
I now want to do it the proper way and am trying to do the python -m codegen && isort . && black . locally.
As a sanity check I'm running the commands in the master branch.
However I have to remove the following from pyproject.toml to get codegen to work.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A similar bug was fixed by: 67d4bf5
So I did the same things and it now works locally.
Fixes #64