Skip to content

chore: readme update with unofficial clients #407

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

Merged
merged 8 commits into from
Feb 25, 2025
Merged

chore: readme update with unofficial clients #407

merged 8 commits into from
Feb 25, 2025

Conversation

rukh-debug
Copy link
Contributor

LMK if the client list are on the appropriate part of the README or not.

Copy link
Collaborator

@tessus tessus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, you put it at the probably worst possible location. ;-)

e.g. the feature flags are a subsection of build from source and you wedged it in between.

Let's put it at the end on the same level as Usage. (most projects put references or alternate projects at the end.)

## 3rd party clients

1.
2.
3.

P.S.: The Table of Contents should then also be updated.

@rukh-debug rukh-debug requested a review from tessus February 23, 2025 22:20
Copy link
Collaborator

@tessus tessus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, once again it is in between subsections. Give me 2 minutes.

@tessus
Copy link
Collaborator

tessus commented Feb 23, 2025

@rukh-debug I made a few updates. Please have a look.

Are you ok with the update?

P.S.: We don't need Here are few third party app and UIs for rustypaste, since the section heading already says it all.

@rukh-debug
Copy link
Contributor Author

My bad. LGTM now.

@tessus
Copy link
Collaborator

tessus commented Feb 24, 2025

@rukh-debug I saw that you resolved the conversations. I'm just wondering why you did that. I didn't see that you committed the suggestions nor that you pushed any additional commits.

Please resolve conversations only after they have been resolved.

P.S.: Unless I missed something, in which case please let me know.

@rukh-debug
Copy link
Contributor Author

Pardon my ignorance, I’m still learning how pull requests work. I was actually wondering where the branch containing these new changes is located. I just realized I need to make those changes in my own branch first.

Copy link
Contributor Author

@rukh-debug rukh-debug left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

docs(readme): update location again

rukh-debug and others added 4 commits February 24, 2025 17:15
Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
@rukh-debug
Copy link
Contributor Author

Please let me know if there is anything else I need to do from my end. I believe it's finally resolved. :)

Copy link
Owner

@orhun orhun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@orhun orhun merged commit 38b1f3f into orhun:master Feb 25, 2025
9 checks passed
@rukh-debug rukh-debug deleted the patch-1 branch February 28, 2025 17:58
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 this pull request may close these issues.

3 participants