Create github action for updating xsd and api docs (sandcastle)?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, powershell
- Domain
- ci-cd, documentation
Research direction
Start from the linked scripts/update-xsd-file.ps1 and list what it reads, runs and writes before creating any workflow. Then inspect how the site's XSD and API docs are currently generated and where the output belongs. Done means a GitHub Actions workflow that runs the same update steps and leaves the regenerated docs in the repository or a pull request.
Written by the indexing model from the issue text.
Description
- Dominant language
- HTML
- Stars
- 6
- Forks
- 24
- Avg merge
- 5m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 NLog/NLog.github.io
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
NLog/NLog.github.io#267 · 1 comment ·
-
Remove old pagesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
NLog/NLog.github.io#263 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
NLog/NLog.github.io#268 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 38/100
NLog/NLog.github.io#266 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 32/100
NLog/NLog.github.io#162 · 6 comments ·
All issues in NLog/NLog.github.io
Similar issues
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
commons-app/apps-android-commons#7341 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
good first issue P3-low security
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 70/100