-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MULTI-GITTER PR: migration github-config-and-gitignore-changes #240
Conversation
Reviewer's Guide by SourceryThis PR updates various GitHub configuration files and documentation to align with current standards. The changes primarily focus on improving contribution guidelines, updating issue templates, and standardizing repository settings. Class diagram for GitHub configuration changesclassDiagram
class RepositorySettings {
- description: String
- homepage: String
- topics: List<String>
- has_issues: Boolean
- allow_rebase_merge: Boolean
+ teams: List<Team>
+ branches: List<Branch>
+ labels: List<Label>
}
class Team {
- name: String
- permission: String
}
class Branch {
- name: String
- protection: Protection
}
class Protection {
- required_status_checks: StatusChecks
- enforce_admins: Boolean
- restrictions: Restrictions
}
class StatusChecks {
- strict: Boolean
- contexts: List<String>
}
class Restrictions {
- users: List<String>
- teams: List<String>
}
class Label {
- name: String
- color: String
- description: String
- aliases: List<String>
}
RepositorySettings --> Team
RepositorySettings --> Branch
RepositorySettings --> Label
Branch --> Protection
Protection --> StatusChecks
Protection --> Restrictions
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @rmenner - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Surge demo deployment failed! 😭 |
…thub workflow files
d5226ca
to
8ddc646
Compare
Summary by Sourcery
Revise documentation and GitHub configuration files to improve clarity and update settings. Modify CI workflows to use abstract node versions for testing. Update repository settings to include new team permissions and label colors.
Enhancements:
CI:
Documentation: