Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: Avoid "deprecated" at old repository #17

Closed
franz-josef-kaiser opened this issue Feb 9, 2024 · 3 comments · Fixed by Rookout/piper#126
Closed

Fix: Avoid "deprecated" at old repository #17

franz-josef-kaiser opened this issue Feb 9, 2024 · 3 comments · Fixed by Rookout/piper#126

Comments

@franz-josef-kaiser
Copy link

I went the Argo Projects README and saw a link to your projects repository. After following the link, I found a "deprecated" notice and filed an issue at the Argo Project to have the link to your repo removed. Gladly @agilgur5 spotted my mistake and correctly hinted, that you might not want to name it "deprecated", but MOVED TO NEW LOCATION instead. I guess most people will read it like me: Your project is unmaintained and gone. Hope you can fix that as your project is something worth keeping around.

@GoshaDo
Copy link
Contributor

GoshaDo commented May 12, 2024

@franz-josef-kaiser Hi thanks for the feedback, link in ArgoWorkflows repo fixed thanks to @agilgur5 . Closing the issue.

@GoshaDo GoshaDo closed this as completed May 12, 2024
@agilgur5
Copy link

Rookout/piper#126 hasn't been merged though, that's what the issue is about, not Argo's link. There are likely other old links to the old repo from various places.

I don't think this should be closed until the old repo's README is fixed, since that's what the issue is about.

@agilgur5
Copy link

Rookout/piper#126 hasn't been merged though

It's merged now 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants