Change Log
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- content, documentation
Research direction
The issue names no file, test, or entry point. Start by inspecting the repository’s documentation structure and contribution workflow to find where a changelog would belong and how content is added. Done means the repository has an agreed changelog location and a clear way to record new supportability content.
Written by the indexing model from the issue text.
Description
Can a changelog be added so we can quickly see new content when it's added?
- Dominant language
- PowerShell
- Stars
- 78
- Forks
- 60
- Avg merge
- 5h 24m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/AzureLocal-Supportability
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure/AzureLocal-Supportability#253 · 1 comment ·
All issues in Azure/AzureLocal-Supportability
Similar issues
-
check:passed streams:add
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Automattic/safe-publish#593 ·
-
channels:add check:passed
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-workshop#3774 ·