AURO MIGRATION: Update Templates to v2

[chrisfalaska]

Resolves AlaskaAirlines/auro-cli#30

Summary by Sourcery

Update the required status checks for the main and beta branches to include test (20.x) and test (22.x), and remove outdated issue templates, labels, and workflows.

CI:

• Update required status checks to include test (20.x) and test (22.x).

Tests:

• Remove outdated test workflows.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the Auro templates to v2. It includes changes to the settings, pull request template, and issue templates. It also removes old workflows and issue templates.

Flow diagram of updated GitHub issue templates

flowchart TD
    A[Issue Creation] --> B{Select Template Type}
    B -->|Bug Report| C[Bug Report Template]
    B -->|Feature Request| D[Feature Request Template]
    B -->|Support Request| E[Support Request Template]
    B -->|Story| F[Story Template]
    B -->|Task| G[Task Template]
    B -->|Group| H[Group Template]

    C --> I[Project Assignment<br/>AlaskaAirlines/19]
    D --> I
    E --> I
    F --> I
    G --> I
    H --> I

    subgraph Bug Report Details
    C --> J[Browser Selection]
    C --> K[Platform Selection]
    C --> L[Reproduction Steps]
    C --> M[Version Info]
    end

Loading

File-Level Changes

Change	Details	Files
Updated status check contexts to use the 'x' suffix for test branches.	Changed 'test (20)' to 'test (20.x)'. Changed 'test (22)' to 'test (22.x)'.	.github/settings.yml
Removed labels from the settings file.	Removed all label definitions.	.github/settings.yml
Simplified the pull request template.	Removed the 'Summary' section. Removed the 'Type of change' section. Kept the 'Resolves' and 'Checklist' sections.	.github/PULL_REQUEST_TEMPLATE.md
Added new issue templates.	Added a bug report issue template. Added a general support issue template. Added a story issue template. Added a feature request issue template. Added a task issue template. Added a group issue template.	.github/ISSUE_TEMPLATE/bug_report.yaml .github/ISSUE_TEMPLATE/general-support.yaml .github/ISSUE_TEMPLATE/story.yaml .github/ISSUE_TEMPLATE/feature_request.yaml .github/ISSUE_TEMPLATE/task.yaml .github/ISSUE_TEMPLATE/group.yaml
Added a security policy.	Added a security policy markdown file.	.github/SECURITY.md
Removed old issue templates.	Removed the old bug report issue template. Removed the old feature request issue template. Removed the old general support issue template.	.github/ISSUE_TEMPLATE/bug_report.yml .github/ISSUE_TEMPLATE/feature_request.yml .github/ISSUE_TEMPLATE/general-support.yml
Removed old workflows.	Removed the addToProject workflow. Removed the autoAssign workflow.	.github/workflows/addToProject.yml .github/workflows/autoAssign.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[github-actions]

Surge demo deployment failed! 😭

[sourcery-ai]

Hey @chrisfalaska - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

suggestion: Remove repeated sentence

This sentence is already present in the template before the changes. Removing the repetition will make the template cleaner.

Suggested change

	# Alaska Airlines Pull Request
	Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
	**Resolves:** # (issue, if applicable)
	## Summary:
	_Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project._
	## Type of change:
	Please delete options that are not relevant.
	- [ ] New capability
	- [ ] Revision of an existing capability
	- [ ] Infrastructure change (automation, etc.)
	- [ ] Other (please elaborate)
	Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
	# Alaska Airlines Pull Request

[chrisfalaska]

We identified an issue with the auro-cli Multi-Gitter, which committed the changes directly to main, bypassing the PR process.

We will refine the Multi-Gitter process to prevent this in the future.

As a result, the changes were committed, making this PR unnecessary. Closing PR.