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

🚧Improve issue number validation #35

Closed
6 tasks done
CalvinWilkinson opened this issue Jun 27, 2024 · 0 comments · Fixed by #37
Closed
6 tasks done

🚧Improve issue number validation #35

CalvinWilkinson opened this issue Jun 27, 2024 · 0 comments · Fixed by #37
Assignees
Labels
💎enhancement An improvement on something high-priority High Priority preview Done while in preview

Comments

@CalvinWilkinson
Copy link
Member

CalvinWilkinson commented Jun 27, 2024

Complete The Item Below

  • I have updated the title without removing the 🚧 emoji.

Description

Improve the issue number validation process when creating pull requests by verifying that the issue has not already been closed. This would indicate that the issue is complete and should not be used.

Also, if the issue exists and is already closed, display a proper error message.

Acceptance Criteria

The items to complete to satisfy the Definition of Done.

ToDo Items

The items to complete to satisfy the Definition of Done.

Issue Dependencies

No response

Related Work

No response

Additional Information:

Unit Tests

Reasons for local unit test execution:

  • Unit tests might pass locally but not in the CI environment during the status check process or vice-versa.
  • Tests might pass on the developer's machine but not necessarily on the code reviewer's machine.
  • If you notice that the test status check has passed but the test failed locally, please notify a project maintainer!

💡Warning💡
If the unit tests pass remotely and are not executed locally, this means we could be letting a bug slip into production.
Though bugs will always exist in some capacity, we should all do our part to help prevent them from happening.

Change Type Labels

Change Type Label
Bug Fixes 🐛bug
Breaking Changes 🧨breaking changes
New Feature ✨new feature
CICD Changes ♻️cicd
Config Changes ⚙️config
Performance Improvements 🏎️performance
Code Doc Changes 🗒️documentation/code
Product Doc Changes 📝documentation/product

Priority Type Labels

Priority Type Label
Low Priority low priority
Medium Priority medium priority
High Priority high priority

Code of Conduct

  • I agree to follow this project's Code of Conduct.
@CalvinWilkinson CalvinWilkinson self-assigned this Jun 27, 2024
@CalvinWilkinson CalvinWilkinson added high-priority High Priority preview Done while in preview 💎enhancement An improvement on something labels Jun 27, 2024
@CalvinWilkinson CalvinWilkinson added this to the v1.0.0-preview.4 milestone Jun 27, 2024
CalvinWilkinson added a commit that referenced this issue Jun 27, 2024
CalvinWilkinson added a commit that referenced this issue Jun 27, 2024
* Start work for issue #35

* enhance: improve issue number validation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💎enhancement An improvement on something high-priority High Priority preview Done while in preview
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant