Closed 0scvr closed 8 months ago
The change looks fine, but looks like code style checks are moaning. Running black should resolve this, I assume it's because of the very long line that the set_string
becomes with this patch.
Still a red cross, you should be able to enable CI on your fork to get faster feedback, running make check
locally should also work.
Same check is complaining, if you just run black on the file it should do the formatting for you. Is make check
passing locally for you?
Same check is complaining, if you just run black on the file it should do the formatting for you. Is
make check
passing locally for you?
make gives me errors. I think pipenv is the problem here.
You can also run black --check *
to confirm this specific check. There may be others, but I think this is probably the only one.
Please follow these steps before submitting a new Pull Request to Guake:
rebase on latest HEAD:
hack your change
to execute the code styling, checks and unit tests:
describe your change in a slug file for automatic release note generation, using:
and edit the created file in
releasenotes/notes/
. You can see howreno
works usingpipenv run reno --help
.Please use a generic slug (eg, for translation update, use
translation
, for bugfix usebugfix
,...)create new commit message
If your change is related to a GitHub issue, you can add a reference using
#123
where 123 is the ID of the issue. You can usecloses #123
to have GitHub automatically close the issue when your contribution get mergedSemantic commit is supported (and recommended). Add one of the following line in your commit messages:
Fixes #2205