GSoC Contribution Interest – Pin Projects to Launcher (Entry Task Done)

70 views
Skip to first unread message

Kunaljit Kashyap

unread,
Mar 26, 2026, 5:20:48 AM (11 days ago) Mar 26
to catrobat
Hello mentors,
My name is Kunaljit Kashyap, and I’m from India.

I’m interested in the “Pin projects to the Android launcher (Play as app shortcuts)” project. As a beginner in open-source, I initially made a mistake by creating a pull request to the main branch. I’m thankful to Wolfgang Slany for guiding me to follow the proper contribution guidelines on GitHub.
After that, I spent a good amount of time understanding the contribution workflow, project structure, and guidelines of Catrobat. Then I moved on to the entry task, explored the codebase, and successfully completed it.
As a first-time contributor, it was quite challenging, but my interest in open source kept me motivated throughout the process. I would really appreciate your feedback on my work and guidance on the next steps.

Would love to contribute to this project!
Best regards,
Kunaljit Kashyap

Wolfgang Slany

unread,
Mar 26, 2026, 8:45:42 AM (10 days ago) Mar 26
to catrobat
Thanks a lot!!!!

Kunaljit Kashyap

unread,
Mar 27, 2026, 2:57:08 AM (10 days ago) Mar 27
to catrobat

Hi Wolfgang,

My name is Kunal. I have completed the entry task for the "Pin projects to the Android launcher" GSoC 2026 project idea.

Quick question: The entry task requires "a green GitHub Actions run link from your fork." Catroid's main.yml workflow skips on forks because it requires Catrobat's private runners. My current CI run shows Repo Check done, Code Analysis done, Unit Tests done but overall status is "Skipped."

Should I: a) Submit the current skipped run as the CI link, or b) Add a separate simple workflow to get a green status?

Thank you for your time.

Best regards, Kunal GitHub: kunaljit3006

Wolfgang Slany

unread,
Mar 27, 2026, 4:05:40 AM (10 days ago) Mar 27
to catrobat
Dear Kunal,

Thanks a lot. Yes, please just include the test results for your tests from your local execution log of the tests, that is fine. 

All the best,
Wolfgang

Reply all
Reply to author
Forward
0 new messages