Replace label in skills-issue--developer.md

[ExperimentsInHonesty]

Overview

We need to change the ready for label on the skills-issue--developer.md issue template so that the merge team can handle more of the issue reviews.

Action Items

• Open the files /.github/ISSUE_TEMPLATE/skills-issue--developer.md
• In the following text, replace ready for dev lead label with ready for merge team label

          - If you have any questions about estimating the issue you choose, please add them to the issue, put the issue in the "Questions/ In Review" column, and add the labels `ready for dev lead` and `Status: Help Wanted`

• Push your issue branch to your fork of the website repository, as described in Section 3.1.a of CONTRIBUTING doc, for example: git push --set-upstream origin test-update-labels-1234

• The response from the push command will include the URL for creating a pull request. Copy/Paste the URL for creating the Pull Request for later.

• Browse to your fork of the website repository and click Settings

  Screenshot of Repository Settings

  

• Change the default branch to the new issue branch

  Screenshot of Default Branch Setting

  

• Further down on the settings page under Features, check the Issues checkbox

  Screenshot of Issues Checkbox

  

• From the Issues page, click "New Issue" then locate the template updated by your issue, and click "Get Started" to open the issue template.

• Copy the URL of the issue creation page and save for later use.

• Verify the appearance of the issue template.

• Complete the Pull Request process by visiting the URL saved from the push command.

• In the PR copy/paste this text immediately before the section "Screenshots of Proposed Changes Of The Website"

 ### For Reviewers
- Use this URL to check the updated issue template: [INSERT URL of issue creation page]

• Replace the text in the square brackets (as well as the square brackets) with the URL of the updated issue template in your fork of the repository
• Submit your pull request with your changes for review
• After PR is merged, be sure to follow the steps above to change your default branch back to gh-pages and to disable Issues feature

Resources/Instructions

For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/.github/ISSUE_TEMPLATE/skills-issue--developer.md?plain=1

• This issue is part of Issue Making Issue EPIC: Replace ready for dev lead with ready for merge label in some of our issue templates  #7602

[HackforLABot]

Hello @dvernon5, we appreciate you taking on this issue, however it looks like you're already working on another issue at this time. Please wait until your current issue is merged before taking on another issue. :)

We are going to unassign you from this issue so you can focus on your current issue.

Hfla appreciates you! :)

[HackforLABot]

Hi @dvernon5, HfLA appreciates your interest in this issue, but please note that it is in the "New Issue Approval" column of the Project Board because it has not been finalized, approved, or prioritized, and so it is not ready for assignment. For this reason, you have been unassigned from this issue. Please remember to assign issues only from the "Prioritized Backlog" column.

The only exceptions to this rule are if you are writing an issue and the Draft label is applied, or if you are self-assigning to your "Pre-work Checklist" (the issue includes the Complexity: Prework label).