🚀 Join Cloudinary's Hacktoberfest!

Open
#32 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
react-native, typescript

Research direction

The issue does not name a source file, test, entry point, or specific change in the cloudinary-react-native repository. Start by reviewing the SDK and its contribution guidance, then choose and scope a concrete enhancement, bug fix, or documentation change. Done is not defined until a specific contribution and acceptance criteria are agreed.

Written by the indexing model from the issue text.

Description

Hacktoberfest is here! And we’re excited to invite you to explore and contribute to our Cloudinary SDKs on GitHub!

Whether you’re a seasoned contributor or new to Open Source, this is a great opportunity to get involved, suggest improvements, and help shape our SDKs.

🛠️ Here’s what we’re looking for:

  • Explore our SDKs and suggest enhancements.
  • Report bugs, improve documentation, or offer new ideas.
  • Help us make the developer experience even better!
  • Meaningful contributions will be eligible for exclusive Cloudinary swag, learn more about the requirements on our blog post

Let’s build something amazing together! 🎉

Dominant language
TypeScript
Stars
28
Forks
21
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudinary/cloudinary-react-native

All issues in cloudinary/cloudinary-react-native

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.