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

Add a proper PR / Issue template to this repo #74

Open
GoliathLabs opened this issue Jan 25, 2022 · 3 comments
Open

Add a proper PR / Issue template to this repo #74

GoliathLabs opened this issue Jan 25, 2022 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@GoliathLabs
Copy link
Member

Hello,
we may want to add a proper template for issues and PR requests to this repo, so that we can get useful information in case of issues or a proper description for new features and pull requests.

@GoliathLabs GoliathLabs added documentation Improvements or additions to documentation enhancement New feature or request labels Jan 25, 2022
@GoliathLabs GoliathLabs self-assigned this Jan 25, 2022
@T0biii
Copy link
Member

T0biii commented Jan 25, 2022

maybe we should then use a template for all our Repos?
In this Repo: https://github.com/freifunkMUC/.github you can place PR / Issue templates as well.

@GoliathLabs
Copy link
Member Author

@T0biii That's a good idea. Is it possible that the templates are overwritten in certain repositories, since it's hard to find templates that fit them all?

@T0biii
Copy link
Member

T0biii commented Jan 26, 2022

@T0biii That's a good idea. Is it possible that the templates are overwritten in certain repositories, since it's hard to find templates that fit them all?

yea i think so, you can overwrite it, just create a template in the repo where you dont want it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants