kaxil / boring-cyborg Goto Github PK

Is there a way to automatically add a label when an issue/PR is created? For example, by making the trigger the root directory (for example, using * in the config).

The JMRI[https://github.com/JMRI/JMRI] build process includes a current-draft-note file that's meant to accumulate text for the eventual release note.

Is there a way to label PRs that don't include an update to that file? That would serve as an automated reminder that people should please include something about their PR in that file.

I have a currently open PR here, specifically linking to the files (and paths) changed: https://github.com/sailpoint-oss/developer.sailpoint.com/pull/28/files

My boring-cyborg.yml in .github/: https://github.com/sailpoint-oss/developer.sailpoint.com/blob/main/.github/boring-cyborg.yml

The GitHub application is installed, has its permissions, and on all repositories:

Am I missing something?

It would be great to add support for automatically commenting on a PR/issues when specific labels are added by maintainers. There's a great Github action that shows how this could work: https://github.com/peaceiris/actions-label-commenter

The use case is: Adding a label to a PR such as "needs-documentation", and a bot responding with what that entails to the contributor.

I've created a similar comment on the actions-label-commenter github action here - peaceiris/actions-label-commenter#24 (comment)

Just adding an issue so I can get a notification when this has been deployed 😄 👍

Hi @kaxil are you using this with Github Enterprise? It would be good to know before I go down a rabbit hole...
Thanks

We've just enabled the bot (nice work by the way, very helpful 👍 ) in our repository, but we aren't getting checks noting if the PR is up to date with the target branch or not.

Having looked at the code am I right in saying it's hard-coded to only work against "master" specifically? This is notable because "master" is not our default/mainline branch.

If the above is the case, would it be possible in addition to check the mainline to have a second check for the target branch?

Would it also be possible to list the number of commits behind master/target branch (appreciate that this number may become stale if master moves on further).

Thanks!

As a maintainer of multiple repos, it would very nice if there was a way to configure organisation defaults (without needing to specify a .github/boring-cyborg.yml file, but optionally being able to do so).

• Some of the config is shared across multiple repos (i.e.:)
  • title validation
  • issue links in description
  • welcome messages
• With the option to extend for specific repos (to add repo-specific:)
  • custom file labelling
  • check branch up-to-date

I've seen a few GitHub apps with something like this.

I'd be open to personally putting up an AWS service if we needed to add storage or something - happy to look into this myself when I find the time.

looks like if a PR are labelled a draft this bot does not label them.

I think it should :)

Currently only basic label config is supported:

labelPRBasedOnFilePath:
  schema:
    - database/migrations/*

Supporting more advance options (specifically color and description) would add a lot of power to the tool (particularly if combined with #15)

Example:

labelPRBasedOnFilePath:
  - label: schema
    files: ['database/migrations/*']

  - label: 'legacy/models :fire:'
    color: '#f04411'
    description: 'Warning: This PR touches the legacy data models.'
    files:
      - lib/models/*
      - lib/models/**/*

I want to add a label based on the PR description. Suppose I write hotfix on my pr description. I want it to be added on the label as well.

Is there any way to do that?

Hello,

In projects, it happens that someone pull request points to the wrong source branch eg.
apache/airflow#8968 . In this case, the proposed changes are huge. Often, the source branch is also not a branch from which pull requests can be expected.

While waiting for the changes to be merged, it happens that the developers merge the master to feature branch to be able to use feature branch directly (installation directly from Git). These pull requests cannot be implemented also.

What can we do about it to support a community that makes pull requests invalid?

Greetings,

verifyTitles suddenly fail to fire in my private repository a few hours ago. The logo for the test results didn't even appear. But the labelPRBasedOnFilePath works fine.
How can I solve it? Is there any log I can debug? Thanks.

Hi,

I've installed this app today and put this config: https://github.com/ansible-community/collection_migration/blob/master/.github/boring-cyborg.yml.

I've reopened ansible-community/collection_migration#339 to see how it works but it didn't add any labels.

Could you please check if the app actually receives events? Also, am I using path globs correctly?

Is it possible to change the name of the bot so it isn't a bot name "boring-cyborg" commenting?

Would you be interested in adding the capability to label PRs based on the memberships of the user who opened it? In projects that have a core contributor team that merge their own PRs once approved, it can be useful to flag PRs from users who don't have merge permissions. Such PRs need to be merged by someone in the core team.

I am willing to open a PR to add this functionality if you're open to adding it.

Does this work for private repos?

We've added the extension and the config file but nothing seems to be happening?