[Purge] Remove inactive tool: piroutte #1518
Draft
Conversation
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
rphair
approved these changes
Jun 27, 2025
Collaborator
rphair
left a comment
rphair
left a comment
There was a problem hiding this comment.
Would also be happy to bump this over to an outdated tag if that structure is created.
Member
|
I agree that this would be the first good example for such an outdated tag. To ensure that it is not removed once it receives enough reviews, it is better to make the PR a draft for the time being. |
Collaborator
|
(before this branch gets too old) manually resolved merge conflict with #1525. |
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
This PR removes the builder tool piroutte from the Developer Portal.
Rationale
Highlight
This repository might be one of the tools that deserve an "outdated" label which would not remove the tool entirely and keep it as an honorable mention. Such an idea was explored in a conversation found in the parent issue #1485 with @katomm.
This PR is a good example to serve as a discussion point to justify a new "outdated" tag, as this tool it serves a unique enough domain. It can be argumented that keeping it in the developer portal can foster newer research initiatives based upon this.
Or not.