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

[48h Knative] Good first issues #1898

Closed
1 of 4 tasks
rhuss opened this issue Nov 23, 2023 · 3 comments
Closed
1 of 4 tasks

[48h Knative] Good first issues #1898

rhuss opened this issue Nov 23, 2023 · 3 comments
Assignees
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@rhuss
Copy link
Contributor

rhuss commented Nov 23, 2023

👋 Hello awesome contributor!

Are you excited about Knative and open-source development? You're in the right place! This is a mini-project for the upcoming 48h Knative event—a 48-hour hackathon designed to boost contributions to the Knative Client project. For more details, check out Issue #1842.

🎯 Project Description

This project is pretty simple & straightforward. Pick and complete as many issues labeled with kind/good-first-issue. Feel free to decide how to approach it in group or on your own. Usually good first issues are very approachable cleanup, removal and smaller fixes.

You find all those issues with this query

🌟 Benefits

Improve the health of Client code base.

🛠 Difficulty Level

Easy

👥 Recommended Team Size

1 - 3

🎉 Expected Outcome

As many issues completed as possible.

🤝 Mentor

@rhuss / @dsimansk

📝 Additional Information

🌐 Entrypoints


📋 Organizer Checklist

  • Added to Project Board
  • Proposal Reviewed
  • Assigned a Mentor
  • Expected Outcome define
@AniketTripathi05
Copy link

how should i contribute to this?

@rhuss
Copy link
Contributor Author

rhuss commented Dec 4, 2023

@AniketTripathi05 If you are interested, we can go through the good first issues, and you can pick one which is interesting for you. We can do this right after the kickoff on Wednesday.

Copy link

github-actions bot commented Mar 6, 2024

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 6, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
Status: Done
Development

No branches or pull requests

3 participants