Document steps to bring a timeliner build into Avalon - #110
Merged
Merged
Conversation
cjcolvar
approved these changes
Mar 26, 2026
cjcolvar
left a comment
cjcolvar
left a comment
There was a problem hiding this comment.
This seems good for now. Better to have it documented somewhere to start with and we can always move it later. 🙂
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
2 participants
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.
Document the steps to bring the timeliner build into Avalon in the
README.md.Since the
README.mdis more for third-party stakeholders, if there's another better-suited place to put this information other than here, that'd be great as well.