-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
feat(docs-utils,dgeni,design-land): separate design docsgen #2968
Closed
griest024
wants to merge
0
commits into
graycoreio:develop
from
griest024:feat/dgeni/design-pipeline
Closed
feat(docs-utils,dgeni,design-land): separate design docsgen #2968
griest024
wants to merge
0
commits into
graycoreio:develop
from
griest024:feat/dgeni/design-pipeline
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
griest024
added
docs
This issue is related to documentation
status: awaiting merge
This PR has met all the requirements for merge and is waiting on an admin
tools: dgeni
@daffodil/tools-dgeni
and removed
status: awaiting merge
This PR has met all the requirements for merge and is waiting on an admin
labels
Aug 13, 2024
griest024
changed the title
feat(docs-utils,dgeni): separate design docsgen
feat(docs-utils,dgeni,design-land): separate design docsgen
Aug 13, 2024
griest024
added
the
status: awaiting merge
This PR has met all the requirements for merge and is waiting on an admin
label
Aug 14, 2024
griest024
force-pushed
the
feat/dgeni/design-pipeline
branch
from
August 14, 2024 18:14
3ff17ff
to
23ff70e
Compare
griest024
added a commit
that referenced
this pull request
Aug 14, 2024
griest024
added a commit
that referenced
this pull request
Aug 14, 2024
griest024
added a commit
that referenced
this pull request
Aug 14, 2024
griest024
added a commit
that referenced
this pull request
Aug 14, 2024
griest024
added a commit
that referenced
this pull request
Aug 14, 2024
griest024
added a commit
that referenced
this pull request
Aug 14, 2024
griest024
added a commit
that referenced
this pull request
Aug 14, 2024
griest024
added a commit
that referenced
this pull request
Aug 14, 2024
BREAKING CHANGE: design examples have moved from `/docs/design-examples` to `/docs/design/examples` (#2968)
griest024
added a commit
that referenced
this pull request
Aug 14, 2024
griest024
added a commit
that referenced
this pull request
Aug 14, 2024
griest024
added a commit
that referenced
this pull request
Aug 14, 2024
griest024
added a commit
that referenced
this pull request
Aug 14, 2024
griest024
force-pushed
the
feat/dgeni/design-pipeline
branch
from
August 14, 2024 18:15
23ff70e
to
4858161
Compare
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
docs
This issue is related to documentation
status: awaiting merge
This PR has met all the requirements for merge and is waiting on an admin
tools: dgeni
@daffodil/tools-dgeni
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Fixes: #2963, fixes: #2916
What is the new behavior?
also significantly DRYs up the guides and API package pipelines
Does this PR introduce a breaking change?
moves design examples
Other information