-
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
Feature: Generating private repositories #52
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Something I was planning to do since sometime — allow generating private projects via `go-template` Up until now, projects were generated by `go-template` under the assumption that they will always be public — which, isn't always true. Private projects would end up with broken links on their README because shields.io can't reach the project! This commit is the first step in this direction Signed-off-by: notsatan <[email protected]>
The README's for generated projects would now be able to handle cases where the project is private — badges would be hidden or modified based on this Signed-off-by: notsatan <[email protected]>
Update the versions of Go supported Signed-off-by: notsatan <[email protected]>
Apparently some upstream issue with the badges caused a badge on the homepage to break down. This commit should fix that Signed-off-by: notsatan <[email protected]>
Signed-off-by: notsatan <[email protected]>
notsatan
added
documentation
Improvements or additions to documentation
enhancement
New feature or request
labels
Jan 5, 2024
The pre-gen Python script had a typo in the name of a function Signed-off-by: notsatan <[email protected]>
With this commit, the recent changes allowing users to use this template to generate private projects have been documented in the project README Signed-off-by: notsatan <[email protected]>
Signed-off-by: notsatan <[email protected]>
Signed-off-by: notsatan <[email protected]>
Signed-off-by: notsatan <[email protected]>
This directly relates to #43, with this in place there is no longer a need to decide where to store stderr logs Signed-off-by: notsatan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Up until now, projects were generated by
go-template
under the assumption that they will always be public — which, isn't always true. Private projects would end up with broken links on their README becauseshields.io
can't access the project!This feature intends to resolve this by removing/updating the links on the generated README to ensure private repositories can generate a project with this template and use it right out of box
Type of Change
Review Process
Reviewees:
Reviewers: