Add issues templates #15
Merged
Conversation
This file contains 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
Closed
|
It seems like the bot did immediately create new issues when the PR was created... not exactly the intended behaviour... will it create issues for every new PR? 😂 |
|
IIUC
|
alessandrofelder
requested changes
Oct 4, 2023
There was a problem hiding this comment.
A suggestion for an intermediate solution based on creating issues on release - what do you think @lauraporta ?
alessandrofelder
approved these changes
Oct 5, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
What is this PR
Why is this PR needed?
When the template is used to generate a new repo, issues are not copied. Here we are trying to automatically open the issues at the moment of the creation of the new repository.
What does this PR do?
Adds a GitHub action that should handle the issue creation and markdown files as issues templates.
References
GH action from dpshelio: https://github.com/UCL-COMP0233-22-23/RSE-Classwork/blob/main/.github/workflows/update-issue.yaml
How has this PR been tested?
I think we have to merge it into main to test if it works 🤔
Is this a breaking change?
No
Does this PR require an update to the documentation?
No
Checklist: