As a maintainer,
I need to use GitHub Actions workflow,
so that I can follow community standards.
We want to try GitHub Actions, and if this goes well deprecate TravisCI usage.
3 hours
@isabelcosta, I would like to work on this.
Cannot wait to see you @gaurivn do this 馃
Good luck!
Thank you, I will try my best
@gaurivn please reach ou if you get stuck in any way. I don't know much of GitHub actions but can try to help just as other community members. By the way @Techno-Disaster did a github actions workflow for Flutter :)
@gaurivn please reach ou if you get stuck in any way. I don't know much of GitHub actions but can try to help just as other community members. By the way @Techno-Disaster did a github actions workflow for Flutter :)
Sure thank you @isabelcosta I will ask you both if I need help
How's the PR going? @gaurivn
Working on it will send a PR soon
I don't have the bandwidth to complete working on GitHub actions, therefore making it available.
@gaurivn no problem at all! Thank you for letting us know 馃檹
@isabelcosta hey!May I work on this?
Sure @vj-codes :)
@isabelcosta I found this , is it the correct resource to begin with?
https://docs.github.com/en/actions/language-and-framework-guides/building-and-testing-java-with-gradle#introduction
@anna4j Is this a good OSH issue?If yes ,I would like to make it available for others
Sure looks good to me! @vj-codes
Hey, I would like to work on it and give it a try.
Please help if I get stuck somewhere
@priyanshuone6 assigning you :)
Can I work on this issue?
Can I work on this issue?
Sure go ahead
Hey @anna4j , I've almost completed this task. But I have a doubt... Currently, the built apk is pushed to the repo's apk branch only if the repository is anitab-org/mentorship-android , not on any other forked repositories. So, should I keep it the same or should I also enable forked repositories to be able to generate apk's on their respective apk branch ?
Umm no I don't think enabling apk generation on forked repos is required
One more doubt @anna4j ... Should I remove .travis.yml and generate-apks.sh before sending the PR?
@isabelcosta
One more doubt @anna4j ... Should I remove .travis.yml__ and generate-apks.sh__ before sending the PR?
Could you please confirm this?
@anna4j it's @isabelcosta :)
Hey @anna4j @vj-codes , I've sent a PR. Please review it. Also, the build workflow is not triggered for this PR. Can you please ensure if the GitHub actions is enabled for this repository?
Hey @anna4j @vj-codes , I've sent a PR. Please review it. Also, the build workflow is not triggered for this PR. Can you please ensure if the GitHub actions is enabled for this repository?
Oh it's probably not enabled. But thanks for raising this issue, I'll take it up on Zulip and our meeting too.
Most helpful comment
@gaurivn please reach ou if you get stuck in any way. I don't know much of GitHub actions but can try to help just as other community members. By the way @Techno-Disaster did a github actions workflow for Flutter :)