SSWConsulting / SSWConsulting/SSW.Rules
CI/CD - History.json update process should be moved into the build pipeline
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
@bradystroud @william-liebenberg @wicksipedia
Sometimes users are not set as the last modified by for a rule even though they just modified it. This issue occurs because users aren't forced to have GitHub Actions enabled on their forks. Additionally, created date is not involved in this process, but it should be.
To solve these issues
- Remove the GitHub Action and add a build step in Azure DevOps on the main repo to perform the process
- Add created date to this process
- Remove created date from Netlify CMS
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Locate the existing GitHub Action and the Netlify CMS handling for created dates, then trace the current history update process. Move that process into an Azure DevOps build step, include created dates, and remove created-date handling from Netlify CMS; verify that modified users and created dates are recorded correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, github-actions
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100