SSWConsulting / SSWConsulting/SSW.Rules
Staging environment - Small site to test rules and CodeAuditor to scan
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
cc: @adamcogan @pierssinclairssw @christianmorfordwaitessw @nvhoanganh @tombui99
To Myself,
- Investigate the best way to have a content staging environment for CodeAuditor to scan and users to see their content before it's merged
One option may be to have an Azure Static site that is deployed on PR then scanned. We would need to find the best way to handle multiple PR's
Thanks,
-Brady
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
No files, tests, or entry points are named. Investigate how an Azure Static site could deploy previews for pull requests, allow users to review content before merging, and let CodeAuditor scan each preview. Done means a documented approach addresses multiple simultaneous pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100