Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is contributor specific settings as pull request welcome ? #48

Open
Gruummy opened this issue Jul 16, 2024 · 0 comments · May be fixed by #49
Open

Is contributor specific settings as pull request welcome ? #48

Gruummy opened this issue Jul 16, 2024 · 0 comments · May be fixed by #49

Comments

@Gruummy
Copy link

Gruummy commented Jul 16, 2024

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.

@Gruummy Gruummy linked a pull request Jul 16, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant