Skip to content

Conversation

@aarya-16
Copy link
Contributor

Description

Issue Ticket Number

Fixes #178

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Fix or improve the documentation
  • This change requires a documentation update

Checklist

  • I have followed the contributing guidelines of this project as mentioned in CONTRIBUTING.md
  • I have created an issue ticket for this PR
  • I have checked to ensure there aren't other open Pull Requests for the same update/change?
  • I have performed a self-review of my own code
  • I have run tests locally to ensure they all pass
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes needed to the documentation

@changeset-bot
Copy link

changeset-bot bot commented Sep 30, 2025

⚠️ No Changeset found

Latest commit: f8c0ef4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Sep 30, 2025

@aarya-16 is attempting to deploy a commit to the Cloudinary DevX Team on Vercel.

A member of the Team first needs to authorize it.

@aarya-16
Copy link
Contributor Author

@devpatocld please take a look into this, and let me know.

If you want me to add Cloudinary LTD in contributors in both the package.json changes, I can do that.

There are also assets, images, and videos, which are probably from his Cloudinary cloud account, but I don't have the links to replace them.

Copy link
Contributor

@eportis-cloudinary eportis-cloudinary left a comment

Choose a reason for hiding this comment

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

Hi @aarya-16 ! Thank you for digging up all of these references to Colby. After some consideration, I don't think we actually want to remove him from the lists of contributors (.all-contributorssrc, the two README.mds, and the two package.jsons), as he has made significant contributions to the project, even though he is no longer active. But I think it is really important that we replace him from LICENSE (although I left a note about how exactly to refer to "Cloudinary") - thank you for catching that, and if you revert the other changes, I'll merge this straightaway.

Apologies for the hastily-filed issue which could have been better defined/scoped, and thank you for the contribution!

@ghostdevv
Copy link
Collaborator

ghostdevv commented Oct 3, 2025

I accidentally broke this so I've merged it here with the necessary changes: #184

Thanks! @aarya-16

@eportis-cloudinary
Copy link
Contributor

@all-contributors please add @aarya-16 for docs

@allcontributors
Copy link
Contributor

@eportis-cloudinary

I've put up a pull request to add @aarya-16! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove "colbyfayock" references

4 participants