Closed ishubham21 closed 1 year ago
Thanks for these suggestions. I think the most interesting idea is the 7th. BTW I'm not familiar with GitHub Actions/CI. I don't know what we need to do that. @NikhilM98 what do you think?
BTW I'm not familiar with GitHub Actions/CI. I don't know what we need to do that.
It's possible to research and set-up GitHub Actions and CI in the forks of the repository. After that PR with configuration can be created and manual configuration steps could be shared with @llaske so that Lionel can configure Sugarizer repositories.
Anything else that is important and I missed out.
I guess we can add git pre-commit hooks to lint and test the code.
I guess we can add git pre-commit hooks to lint and test the code.
@NikhilM98 can you please check I have made a PR regarding git pre-commit to run tests.
I suggest to just add a Github action to run unit testing each time a commit is done on dev branch.
Can I work on on this issue or is any one actively working on this?
@NeerajGartia21 PR #381 has made some promising progress with this issue. It has some minor issues such as unnecessary file changes and large number of commits which need to be resolved, but the feature seems to be working fine.
Feel free to test the application and create new issues if you find any bugs in the application.
@NikhilM98 does this issue is open to work. so that i can contribute to it if yes then do suggest me.
@AviGawande no, the issue is close.
@llaske could you please tell me from where i will get to know about 2024 gsoc program. please do reply..
@AviGawande SugarLabs is not yet part of GSoC 2024.
Currently, the repository lacks GitHub Actions/workflows or GitHub CI. Some of the proposed additions are -
merge-conflict
if there's a merge conflict in it - can be done for both master and dev branches.npm test
whenever a PR is made.I'd love to hear suggestions/additions on this. CC @NikhilM98 @llaske