-
-
Notifications
You must be signed in to change notification settings - Fork 786
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
Change the Feature: Administrative
label to feature: spelling
in spell check issue template
#6857
Comments
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as resolved.
This comment was marked as resolved.
Hi @santisecco, thank you for taking up this issue! Hfla appreciates you :) Do let fellow developers know about your:- You're awesome! P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :) |
I have a question. I want to confirm that I understood correctly. Then by "The color of the labels don't have to match those on the hackforla/website repository" are these the labels from_https://github.com/hackforla/website/labels_? Perhaps my question is obvious since by the issue's heading which says "spell check issue template" I can infer that refers to the file github/ISSUE_TEMPLATE/spell-check-audit.md Finally by "then locate the template updated by your issue, and click "Get Started" to open the issue template." is this the file spell-check-audit.md in my fork? |
@urvishp13 Hi Urvish perhaps you can help me out with this doubt |
Also I noticed that in the file "spell-check-audit.md" there's seems to be "back end/devOps" with two extra spaces being "back end/devOps", it's at the start of a new line so I don't know which of the two texts I must use in the label creation. |
I have a blocker: Here's what I've done so far I want to know if that is correct before moving on with the rest. |
Hi @santisecco
I am removing the |
Prerequisite
Overview
We need to change the
Feature: Administrative
label to thefeature: spelling
label in the spell check issue template. We're doing this, so the issues generated from this template are properly labeled.Action Items
Open the file
.github/ISSUE_TEMPLATE/spell-check-audit.md
in your code editor.In the
labels
property, replacewith
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-label-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
Browse to the Issues page, then click Labels
Screenshot - creating labels in the test Repo
Create labels corresponding to each label that was listed in the updated issue template. The color of the labels don't have to match those on the
hackforla/website
repository, but the text of the labels must match exactly.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 as [URL OF ISSUE TEMPLATE] and save for later use.
Verify the changes 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"
Replace the text in the square brackets (as well as the square brackets) with the URL of the updated issue template.
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 the Issues feature.Resources/Instructions
The text was updated successfully, but these errors were encountered: