They're not directly needed by any of the scripts. They should have been
Recommends: in the first place but we couldn't do that for amber-phone
so fix that up now.

The correct way (nowadays) to protect a branch is by using the
protected_branches endpoint
(see https://docs.gitlab.com/ee/api/protected_branches.html)

Fixes #4

Event if we just push 'master' there it might help people to
get a version matching phosh-next.

This allows to add "unnoficial" next branches

Guido Gunther authored Feb 21, 2022 and Guido Gunther committed Mar 07, 2022

Fetch the debs from a 'next' repo and install the debs.

Guido Gunther authored Feb 09, 2022 and Guido Gunther committed Mar 03, 2022

This creates a skeleton release from NEWS and `d/changelog` and local
notes.

Fixes #3

Guido Gunther authored Jul 29, 2021 and Guido Gunther committed Jan 25, 2022

This will grab MRs stored in the git config variable `next.MRS`, merge
them to your projects main branch and push that out as `-next` branch so
people can easily grab new development snapshots.

For setup instructions see the top of the script.

We have a variable 'projects' which has the data already assigned we
want to iterate over.

To access a repository the user must have a valid token and must be be
member of the role maintainer or owner.
Adding a check that prove the ressource can be accessed by the user.

Older versions returned None, we get an exception nowadays.

This makes us only apply the stricter rules to the PureOS space.

The boolean condition was inversed

These are templates for projects in Librem5/debs/.

Guido Gunther authored Apr 22, 2021 and Guido Gunther committed Jul 17, 2021

Setup default branches, merge policies, CI, etc.

Guido Gunther authored Jul 16, 2021 and Guido Gunther committed Jul 17, 2021

Packaging repositories for downstream forks should have a consistent
layout. Check what we did manually before.

This helps projects using the same or similar coding style like phoc,
libhandy, ...

The script downloads the latest CI artifact of a specific MR.
It tries to guess the correct artifact for the Librem5 or if it can't find one
it gives the possibility to manually specify a CI job.
Once found a correct artifact it unzips it and installs it.

Based on https://source.puri.sm/snippets/188

The CI uses
`https://source.puri.sm/Librem5/librem5-ci/raw/master/librem5-pipeline-defintions.yml`
but the correct url is
`https://source.puri.sm/Librem5/librem5-ci/raw/master/librem5-pipeline-definitions.yml`