z0al / commitlint-bot Goto Github PK

Now.sh has forced all new deployments to use v.2 of their platform. This repo does not seem to be setup to work on version 2 at all.

Hello there,

The bot seems not to receive any more info, since today (it was functionnal this last friday ^^), on all our repos. Do you know what's going on ?

Hi, @ahmed-taj

Take a look in this error msg.

Reference:
flyve-mdm/glpi-plugin#386

Example: caarlos0/env#52

I've fixed the commit messages, and the status is now green, but the original list of issues in the bot's comment remains.

Hey! This is really cool! I had a quick drive-by thought; with the GPG Probot App we've talked about how to fix a failed status. As in, what happens when someone commits without verifying their GPG key?

I think there's a similar situation with the commitlint-bot; if I commit a message that wouldn't pass, and the PR gets a ❌ , maybe you can use the Details pane to suggest ways to fix it. This way, it becomes a way for folks to learn on the spot and not be blocked by something they don't know how to do with Git.

For some reason commitlint is not functioning anymore, just wanted to now first if I am the only one experiencing this?

See db-migrate/node-db-migrate#537 for reference, which is missing the commitlint output for an unknown reason. Have reinstalled the bot already to test if this would have been the source of the problem, but unfortunately it seems to be something different. Nothing was changed from the last time it worked though...

I would like to discuss what things I need to consider when supporting custom configuration files in the root repository directory.

More specifically, how can we support .commitlint.yml or .commitlint.json ? I can't see any way to support .js based config files

Any input is welcome!
cc @marionebl

Since I repeatedly receive questions, I will open this ticket here now. The bot message should include a link to the conventions, otherwise new users have no clue at all, what is happening.

So a link pointing the user to the convention, probably https://github.com/conventional-changelog/conventional-changelog/tree/35e60b5be6027fb2784c5103eee111f6f99b045e/packages/conventional-changelog-angular, would be immmensly helpful.

db-migrate/node-db-migrate#549 (comment)

Mostly opening a conversation here, I'm in no rush to do anything. And please don't feel pressure to support my usecases. :)

Soo I have my own bot with this name: https://github.com/paulirish/commitlintbot

However mine only cares about Pull Request titles and doesn't care about actual commit messages. So technically it probably makes more sense to be called commitlint-pr-bot.

I created it as there was no other option at the time, but I'm happy to retire and and point to your project if a few things happen:

• Support linting a PR title
• Support ignoring commit messages
• Supportcommitlint.config.js (#1)
• Support commitlint-config-cz for a project to specify custom types/scopes

Again, we can also agree to keep our projects separate. That's totally fine with me. :) I just wanted to list these out in case you want to create the ultimate feature-rich commitlint bot. 🎉