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

Update GitHub issue templates #319

Merged
merged 1 commit into from
Nov 8, 2024
Merged

Update GitHub issue templates #319

merged 1 commit into from
Nov 8, 2024

Conversation

manuq
Copy link
Contributor

@manuq manuq commented Nov 8, 2024

This is an open-source plugin and now also developed in the open. Remove link to Endless Employees issue tracker. Edit the "public" template to be the sole issue template.

This is an open-source plugin and now also developed in the open. Remove
link to Endless Employees issue tracker. Edit the "public" template to
be the sole issue template.
@wjt wjt merged commit c119326 into main Nov 8, 2024
3 checks passed
@wjt wjt deleted the remove-internal-bugtracker branch November 8, 2024 15:14
@manuq
Copy link
Contributor Author

manuq commented Nov 8, 2024

Honestly I'm new to GitHub templates so I'm not sure if it will work. These were added by @cassidyjames in commit 6f7bb2d . Reading https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser it looks like by removing the cconfig.yml the option for Endless employees should be removed.

@manuq
Copy link
Contributor Author

manuq commented Nov 8, 2024

The chooser is still there but now with the only option we want: https://github.com/endlessm/godot-block-coding/issues/new/choose

Maybe in the future we can have a "feature proposal" template? With a field to justify the educational purposes that the README describes.

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 this pull request may close these issues.

2 participants