feat(template): add project_audience profile, default to solo-internal#325
Merged
Conversation
Member
Author
|
This change is part of the following stack: Change managed by git-spice. |
This was referenced Jun 2, 2026
ApprovabilityA prior Macroscope approval was dismissed. Re-evaluating 8acc326… |
32ea85c to
4b0207d
Compare
f6b67ff to
471148e
Compare
4b0207d to
0c9bfa9
Compare
471148e to
8acc326
Compare
Dismissing prior approval to re-evaluate 8acc326
Introduce a high-level project_audience question (solo-internal | team | public-oss) that cascades defaults across the existing toggles. It only sets each toggle's default — every option stays overridable, and existing projects keep their saved answers on update (additive, no migration needed). Cascade: - solo-internal (new shipped default): internal visibility, no CI, no docs site, light hooks, no community-health files. - team: adds CI + semantic-release/changelog; otherwise stays light. - public-oss: the full stack (the previous default behaviour). Also gate the README ci/release/codecov badges on use_ci/use_semantic_release so a CI-less project no longer ships dead badges, and document the audience profiles in the template's own README. Refs DOT-593
This comment has been minimized.
This comment has been minimized.
e4c3a05 to
6cb0636
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Introduce a high-level project_audience question (solo-internal | team |
public-oss) that cascades defaults across the existing toggles. It only sets
each toggle's default — every option stays overridable, and existing projects
keep their saved answers on update (additive, no migration needed).
Cascade:
light hooks, no community-health files.
Also gate the README ci/release/codecov badges on use_ci/use_semantic_release so
a CI-less project no longer ships dead badges, and document the audience
profiles in the template's own README.
Closes DOT-593
Closes #
Note
Add
project_audienceprofile question and default tosolo-internalproject_audiencequestion to copier.yml with choicessolo-internal(default),team, andpublic-oss, replacing the previous public-OSS-biased defaults.solo-internaldisables CI, docs, heavy hooks, and community-health files;teamenables CI;public-ossrestores the previous full-stack behavior.use_cianduse_semantic_releaseso generated READMEs reflect the chosen profile.project_audience: public-ossto preserve existing test coverage; a newTestAudienceProfilessuite in tests/test_template.py validates cascade behavior for all three profiles.project_audienceare unaffected, but new scaffolds now default tosolo-internalinstead ofpublic-oss.🖇️ Linked Issues
Implements DOT-593, which requested a
project_audienceprofile to shift defaults away from public-OSS for solo/internal use cases.Macroscope summarized 51a39ad.