Hi ....
we also want to continue to use httpbin and found the problem about not maintained original repo.
Yours is the most current fork.
We want to bring our changes also to upstream available.
Would it be ok if we create pull request for your fork ?
As first i would want to create a small pull request to add the following content to the .gitignore file
# Contributer ignore: where all local testing / learning stuff should be located
# in this directory, to not be included in pushes / merges / pull requests
.local
# to not include vscode configfolder in pushes / merges / pull requests
.vscode
# Starting from here: ignore of official maintainers
env/
build/
.. here then the other contents which already exist
I simply would want to prepare for contribution in a transparent way, that everyone can understand in which location savely everything local can be stored inside the local clone of this repo without causing issues in pull requests with not wanted internal content to be published.
Hi ....
we also want to continue to use httpbin and found the problem about not maintained original repo.
Yours is the most current fork.
We want to bring our changes also to upstream available.
Would it be ok if we create pull request for your fork ?
As first i would want to create a small pull request to add the following content to the .gitignore file
I simply would want to prepare for contribution in a transparent way, that everyone can understand in which location savely everything local can be stored inside the local clone of this repo without causing issues in pull requests with not wanted internal content to be published.