Release on main?

[jo-elimu]

Performing a Maven Release directly on the main branch is currently not working on this repository. This is because of the branch protection rule which requires a pull request, and an approval by at least 1 code owner (maintainer) before merging:

---

For model repo, however, we can perform releases directly on the main: https://github.com/elimu-ai/model/actions/workflows/maven-release.yml

That's because the pull request requirement "Require a pull request before merging" has been disabled for that repo.

I suggest we do the same for this webapp repo, to avoid time wasted on release management. In other words; continuing as before by creating a new pull request for each issue, except for releases. Code owners (maintainers) will have access to commit directly to main if they want, but are encouraged to only use this access when performing releases.

[jo-elimu]

@AshishBagdane Thoughts?

[AshishBagdane]

Hi @jo-elimu,

What you're suggesting is:

• We will be allowing only maintainers to commit directly to main in the webapp repo for releases, just like in the model repo, by disabling the Require a pull request before merging setting.

• Regular development will still follow the usual process of creating a pull request for each issue, but direct commits will be permitted only for release management to save time.

Let's do like this!

[AshishBagdane]

Also, see if we could trigger release build on push to main like following by keeping the manual trigger option open:

on:
  push:
    branches:
      - main
  workflow_dispatch:

What do you think?

[jo-elimu]

Also, see if we could trigger release build on push to main like following by keeping the manual trigger option open:

on:
  push:
    branches:
      - main
  workflow_dispatch:

What do you think?

@AshishBagdane Yes, you mean configuring the workflow so that a release is automatically triggered after a pull request has been merged? I agree 💯 that that would be the optimal solution.

[AshishBagdane]

@jo-elimu Exactly!