societe-generale / societe-generale/github-crawler
make ConfigValidator source control specific
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 111
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Summary
we currently have a generic ConfigValidator that we apply for all source control system we manage (Github, GitLab, Azure Devops), but we see a need to sometimes have specific ConfigValidator
Type of Issue
It is a :
- bug
- [x ] request
- question regarding the documentation
Motivation
cleaner code and design
Your Environment
- Version used: 2.0.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.
Research direction
Start by locating the generic ConfigValidator and its uses for GitHub, GitLab, and Azure DevOps, then read how configuration validation is currently wired. Done means the design supports source-control-specific validators for the managed systems while preserving existing validation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, gitlab, kotlin
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100