Link current stack version instead feature releases. #75
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.
Description
When we support stack versions in VPR docs, we used (through our discussion) central release repo [master branch] to link. However, we checked that the master points to future releases, so that VPR docs should catch current stack release versions.
This PR introduces to replace master branch with current branch. Note that, current branch doc links to the current branch version doc, so that our logic pulls current version doc and retrieve stack versions from there.
Closes #74
Test
Command:
bundle exec ruby versioned_plugins.rb --repair --skip-existing --dry-run --output-path=../
Output log: