llaske / sugarizer-server

Sugarizer Server allow deployment of Sugarizer on a local server, for example on a school server.
Apache License 2.0
42 stars 92 forks source link

Adding GitHub Workflows/Actions/CI #293

Closed ishubham21 closed 1 year ago

ishubham21 commented 2 years ago

Currently, the repository lacks GitHub Actions/workflows or GitHub CI. Some of the proposed additions are -

  1. Merge conflict watcher that label PRs as merge-conflict if there's a merge conflict in it - can be done for both master and dev branches.
  2. Welcome first-time contributors (on new PR/issues) with a message.
  3. A codeQL to check vulnerabilities across the repository. This can be configured for 2 cases - when a new PR is created, a CRON job that runs every Monday at 00:00 UTC, maybe?
  4. A workflow to close issues/PR that have not seen any activity in the last 45 days with prior 7-day notice.
  5. Issue templates for - bug reports, documentation updates, and feature request
  6. Pull Request template.
  7. Automated testing that installs the dependencies and runs npm test whenever a PR is made.
  8. Anything else that is important and I missed out.

I'd love to hear suggestions/additions on this. CC @NikhilM98 @llaske

llaske commented 2 years 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?

NikhilM98 commented 2 years ago

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.

NikhilM98 commented 2 years ago

Anything else that is important and I missed out.

I guess we can add git pre-commit hooks to lint and test the code.

dhwaj1902 commented 2 years ago

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.

llaske commented 1 year ago

I suggest to just add a Github action to run unit testing each time a commit is done on dev branch.

NeerajGartia21 commented 1 year ago

Can I work on on this issue or is any one actively working on this?

NikhilM98 commented 1 year ago

@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.

llaske commented 1 year ago

Fixed in https://github.com/llaske/sugarizer-server/pull/384

AviGawande commented 9 months ago

@NikhilM98 does this issue is open to work. so that i can contribute to it if yes then do suggest me.

llaske commented 9 months ago

@AviGawande no, the issue is close.

AviGawande commented 8 months ago

@llaske could you please tell me from where i will get to know about 2024 gsoc program. please do reply..

llaske commented 8 months ago

@AviGawande SugarLabs is not yet part of GSoC 2024.