Make packaging doc a symlink to new doc #17098
Open
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
github-actions
bot
added
area/packaging
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.
Summary
@netdata/agent-sre I think we need only one packaging file, and Costa made https://github.com/netdata/netdata/blob/master/docs/netdata-agent/versions-and-platforms.md that is currently in Learn.
I think the old file can become a symlink, but I see you involve the actual file in a workflow and stuff.
I also recall Austin having some comments on the initial file, so maybe he can commit them to the new file in this PR and then we can request review.
What I did is agnostic to the content inside the old file, and here is where I think you should have a say on it. I just removed the file and made a symlink README so it shows up on the page tree