unibeautify / ci-issues

Public Issues for Unibeautify CI

unibeautify-ci-issues

Public Issues for Unibeautify CI

ci-issues's Issues

CI Job doesn't seem to run

Hi,

First off, I think you've done some amazing job with this tool and I'm looking forward to using it!

I've been trying to integrate this into our repo, but I can't seem to get the CI Job to run. The app is installed on the GitHub account and is tracking the repo.

The job output is here: https://github.com/ISISScientificComputing/autoreduce/pull/1075/checks?check_run_id=1853127986 and it doesn't look like it ran anything.

I tried both a JSON and YAML config but neither worked, this is the current one: https://github.com/ISISScientificComputing/autoreduce/blob/915_enforce_yapf/.unibeautifyrc.yml. It was generated from the config assistant.

Any ideas? I can't seem to find where to look for what went wrong, the details links just go to the main website, and I've added a yapf check in the main CI job just for sanity and that fails as expected

rename branch error

I tried to rename a branch from patch-1 to kabyle-translation and I got an error

Remove status API checks

Most CI tools have removed the status checks in favor of Check Runs. Unibeautify CI should do the same sooner or later.

Branch filtering

From @stevenzeck on October 12, 2018 15:40

Unibeautify CI is great, however if left unchecked it can cause a TON of backlogs in Travis. I forget which repo it was, but Unibeautify was not correct on master. Whenever Renovate created a new branch for a dependency update, Unibeautify CI also created a branch to fix the branch that Renovate created. Scenario example:

1. master, UB CI is failing and has a unibeautify/master branch to fix it
2. Renovate creates a branch for typescript dependency update: renovate/typescript3.x. Travis CI build starts for this branch
3. renovate/typescript3.x also fails UB CI, so UB CI creates a branch to fix it:
   unibeautify/renovate/typescript3.x. Another Travis CI build starts for this branch
4. Open a PR to merge unibeautify/renovate/typescript3.x to renovate/typescript3.x. Travis CI build starts
5. Merge PR, another Travis CI build starts for renovate/typescript3.x

That's 4 Travis CI builds when it only needs 1.

Copied from original issue: Unibeautify/unibeautify#205

Unibeautify CI doesn't work when branch is in another repo

When opening PR's against the main repository, if your PR branch exists in a different repository (such as a forked one), Unibeautify CI does not run.