Skip to content

Latest commit

 

History

History
63 lines (44 loc) · 3.34 KB

labels.md

File metadata and controls

63 lines (44 loc) · 3.34 KB

Labels

We use GitHub labels to signal the status of pull-requests and issues. Here you can find more information about the ones that have some special meaning:

Contents

Bump dependencies

Label Bump dependencies is assigned by the bot to pull-requests that are just upgrading the version of the requirements that were already in the recipe.

These pull-requests will be merged right away without requiring any approval (CI and CLA checks must have passed).

If the pull request modifies anything else, the label won't be assigned, we need to be very careful about false positives.

Bump version

Label Bump version is assigned by the bot to pull-requests that are just adding a new version of the library. The new version should satisfy some extra conditions: sources should provide from the same URL domain as previous versions and the version itself should be valid semver.

These pull-requests will be merged right away without requiring any approval (CI and CLA checks must have passed).

If the pull request modifies anything else, the label won't be assigned, we need to be very careful about false positives.

Infrastructure

Label infrastructure is manually assigned to pull requests that are waiting for something on the infrastructure side. Usually they are blocked and cannot succeed because they need some tools, more memory,... these pull requests won't be marked as stale.

Stale

Label stale is assigned to pull requests without any activity during a long period of time. These pull requests will be closed if they don't get any further activity.

Unexpected Error

Label Unexpected Error is assigned by the CI when the process finishes abnormally. It tries to signal all the pull requests that failed, but didn't provide any meaningful message to the user. Usually it is some random internal error and it won't happen next time the CI runs. The CI will re-start your build automatically, the Github check continuous-integration/jenkins/pr-merge will changed to the status Pending — This commit is being built to signalize as running. In case you restart it manually, by closing/opening the PR, your build will be restarted too, but it will be the last in the CI build queue.

User-approval pending

Label User-approval pending signals the pull request that have been submitted by an user who is not yet approved in ConanCenter. Once the user is approved these pull requests will be triggered again automatically.