Repository navigation
Generate mind map automatically (via GHA) - #348
Merged
Merged
Conversation
… can be used for dependency caching.
spier
marked this pull request as ready for review
September 1, 2021 10:36
spier
requested review from
NewMexicoKid,
cewilliams and
lenucksi
as code owners
September 1, 2021 10:36
Member
Author
This was referenced Sep 1, 2021
Member
|
Cool stuff! 🎉 |
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.
This is part of the solution for #162.
Assuming that a fully automated solution would consist of these steps:
patterns/*.mdfiles intoinnersource-program-mind-map.md(this is different from how this is working today)innersource-program-mind-map.html)This PR solves 2 + 3.
Tasks
book/innersource-program-mind-map.PNG=> we are now just keeping this file in the folder/pattern-categorization, and link to it from/bookUpdate
I noticed that solution step (1) above wasn't necessarily intended as part of #162.
Hence I will leave it out of this PR, and instead file a new issue that describes the idea behind (1) in more detail.