perf: add backwards compatible issue templates #262
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
✅ Deploy Preview for design-insights ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for oss-insights ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
bdougie
approved these changes
Aug 24, 2022
github-actions bot
pushed a commit
that referenced
this pull request
Aug 24, 2022
### [1.2.1](v1.2.0...v1.2.1) (2022-08-24) ### 🔥 Performance Improvements * add backwards compatible issue templates ([#262](#262)) ([af21ab5](af21ab5))
|
🎉 This PR is included in version 1.2.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
0-vortex
added a commit
that referenced
this pull request
Aug 26, 2022
* origin/main: chore(patch): release 1.2.3 [skip ci] fix: correct feature request issue template for good chore(patch): release 1.2.2 [skip ci] fix: correct issue template labelling chore(patch): release 1.2.1 [skip ci] perf: add backwards compatible issue templates (#262)
0-vortex
added a commit
that referenced
this pull request
Aug 26, 2022
* origin/main: chore(patch): release 1.2.3 [skip ci] fix: correct feature request issue template for good chore(patch): release 1.2.2 [skip ci] fix: correct issue template labelling chore(patch): release 1.2.1 [skip ci] perf: add backwards compatible issue templates (#262)
github-actions bot
pushed a commit
that referenced
this pull request
Aug 26, 2022
## [1.3.0-beta.13](v1.3.0-beta.12...v1.3.0-beta.13) (2022-08-26) ### 🔥 Performance Improvements * add backwards compatible issue templates ([#262](#262)) ([af21ab5](af21ab5)) ### 🐛 Bug Fixes * correct feature request issue template for good ([6410fd2](6410fd2)) * correct issue template labelling ([3ce5039](3ce5039)) * Update GitSense API route for repos ([#270](#270)) ([8f7e1c5](8f7e1c5))
|
🎉 This PR is included in version 1.3.0-beta.13 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
ElpisHelle
added a commit
to ElpisHelle/next.js-tailwindcss
that referenced
this pull request
Aug 17, 2023
### [1.2.1](open-sauced/app@v1.2.0...v1.2.1) (2022-08-24) ### 🔥 Performance Improvements * add backwards compatible issue templates ([#262](open-sauced/app#262)) ([af21ab5](open-sauced/app@af21ab5))
ElpisHelle
added a commit
to ElpisHelle/next.js-tailwindcss
that referenced
this pull request
Aug 17, 2023
## [1.3.0-beta.13](open-sauced/app@v1.3.0-beta.12...v1.3.0-beta.13) (2022-08-26) ### 🔥 Performance Improvements * add backwards compatible issue templates ([#262](open-sauced/app#262)) ([af21ab5](open-sauced/app@af21ab5)) ### 🐛 Bug Fixes * correct feature request issue template for good ([6410fd2](open-sauced/app@6410fd2)) * correct issue template labelling ([3ce5039](open-sauced/app@3ce5039)) * Update GitSense API route for repos ([#270](open-sauced/app#270)) ([8f7e1c5](open-sauced/app@8f7e1c5))
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.
What type of PR is this? (check all applicable)
Description
This PR adds issue templates back, not perfect but consistent with our 2.0 templates and pull request templates
Related Tickets & Documents
Mobile & Desktop Screenshots/Recordings
Test it out live over at gs-api.opensauced.pizza
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?