Skip to content

doc: highlighted config.yml file in issue-template-config #25796

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

Merged
merged 1 commit into from
Jun 2, 2023

Conversation

aayushchugh
Copy link
Contributor

changed config.yml to config.yml so that it is highlighted and clearly visible

Why:

I highlighted the config.yml so that it's Cleary visible to new users that you need to create this file to configure issue templates

What's being changed (if available, include any code snippets, screenshots, or gifs):

changed config.yml to config.yml

Check off the following:

  • I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
  • For content changes, I have completed the self-review checklist.

changed *config.yml* to `config.yml` so that it is highlighted and clearly visible
@welcome
Copy link

welcome bot commented Jun 2, 2023

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jun 2, 2023
@cmwilson21
Copy link
Contributor

@aayushchugh Thanks so much for opening a PR! I'll get this triaged for review ⚡

@cmwilson21 cmwilson21 added content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review repositories Content related to repositories and removed triage Do not begin working on this issue until triaged by the team labels Jun 2, 2023
Copy link
Contributor

@skedwards88 skedwards88 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this PR! We'll get this merged down for you.

@skedwards88 skedwards88 added this pull request to the merge queue Jun 2, 2023
@skedwards88 skedwards88 added the ready to merge This pull request is ready to merge label Jun 2, 2023
Merged via the queue into github:main with commit 2b4ddf5 Jun 2, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Jun 2, 2023

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team ready to merge This pull request is ready to merge repositories Content related to repositories waiting for review Issue/PR is waiting for a writer's review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants