GitLab

Our docstrings are checked by pydocstyle not pylint.

According to https://www.gnu.org/licenses/gpl-howto.html

The production sandbox is at flathub.

The sandbox we use is for development and master builds.

.pre-commit-config.yaml:
- flake8 has been removed as it's a wrapper for pyflakes, which parses
the py files itself, meaning it's faster than pylint, but less powerful.
It seems it was not active as we had only two #noqa but no warnings.
- autopep8-wrapper has been removed so the committer is in control.

pre-commit.hook:
- git_pep8_commit_hook has been removed as pylint already checks for
PEP8 conformance.
- pylint is now run after the lightweight pre-commit.com hooks.

Found via ` codespell -q 3 -S *.po -L dur,que,uint`

Fixes #2302

I just got a power cut... and without internet access the
pitivi-flatpak script was not usable. Just assume everything is all
right if we could not retrieve repo infos.

Found with `codespell -q 3 -I ../pitivi--whitelist.txt --skip="*.po,*.svg"`

For example:
flatpak update --user org.gnome.Platform 3.28
Updating in user:
org.gnome.Platform/x86_64/3.28                       flathub 4afe5ccb6990
org.gnome.Platform.Locale/x86_64/3.28                flathub 1d96abcdc97b
Is this ok [y/n]:

flatpak info returns an error if there are multiple versions of the
subpackage installed, requiring one of them to be specified.

For example:
flatpak install --user flathub org.gnome.Platform.Locale 3.24 --reinstall
Installing in user:
org.gnome.Platform.Locale/x86_64/3.24 flathub fabbccbd2dae
Is this ok [y/n]:

Update the flatpak version check as we now require 0.10. Also cleanup
the way we check Sdk version.

Not simply using fatal-criticals as some criticals are outside of
control on the CI server (no dbus running there)

And call the flathub repo... flathub!

Clarifies a bit what the add() method does.

This adds the --init flag which can be used to quickly check the dev env
is set up.

Ideally we should check each component individually whether it should be
installed or set up, not all or nothing.

This is better mantained and it is the future

Spaces are now `\t` so handle them as if they were spaces when
looking for remotes urls.

And recommend to follow the GNOME newcomer guide

Differential Revision: https://phabricator.freedesktop.org/D1952

Differential Revision: https://phabricator.freedesktop.org/D1926

We want to use both pre-commit.com and our own `pre-commit.hook`. Since
the hooks are installed only when setting up the dev env, we can assume
there is one and error out in the pre-commit.hook. Also, we can call
pre-commit.com directly from there, as that's what pre-commit.com's
wrapper is doing.

Differential Revision: https://phabricator.freedesktop.org/D1945