3 ms·

>> Why not a tool that bumps dependencies and let’s you propose yourself? SO it opens an issue and gives you a patch file... Or emails it to you? > Why does i

>> Why not a tool that bumps dependencies and let’s you propose yourself? SO it opens an issue and gives you a patch file... Or emails it to you? > Why does it seem to these tools have converged on the bot-makes-PR implementation? Because git and the PR is the common choke point that every one knows and loves. A lot of dev's look down on "patches"... there are tons of people who happily use linux who think that all kernel devs are stupid cause of bugzila/patches and email could not possibly work.

keybored 3y ago
Patch files? Normal tools change files. If I `sed -i` in my project I just change the files in my project. Then I (separately) can add and commit them. Same for (for example) linting tools. This bot-PR workflow is outside of that normal.
- partdavid 3y ago
  You mean on some individual person's laptop when that person remembers to run it?
  - keybored 3y ago
    Like most things.
    - OJFord 3y ago
      But the whole point is not to have to do that. What you're asking for is basically just `npm upgrade` or `cargo upgrade` or whatever? The point of Renovate, Dependabot etc. is exactly the automated/scheduled running of those package manager updates.
      - keybored 3y ago
        Sigh. The answer to why they are this way is that it’s the whole point that they are this way.
        OJFord 3y ago
        Well yes? You're complaining that a motorbike has an engine when you're perfectly capable of and would rather power it with your own two legs.
        keybored 3y ago
        What a great comparison.
- zer00eyz 3y ago
  A PR is easy to automate, hook into, an preserves ownership of the commit. Yes it bypasses YOUR workflow, but a PR works for everyone who uses GitHub. If you want something else that works for everyone who uses GitHub it's an issue, or an email with a patch file. Why a patch file. DO you want to own the change the bot suggested? There are a lot of orgs where the ownership matters more than the linting. You could just make the change yourself, sure, and then run it through your normal workflow... then your the author and commuter of the change...
  - keybored 3y ago
    I stepped into the wrong workflow synagogue it seems.

keybored 3y ago

Patch files? Normal tools change files. If I `sed -i` in my project I just change the files in my project. Then I (separately) can add and commit them. Same for (for example) linting tools. This bot-PR workflow is outside of that normal.

partdavid 3y ago
You mean on some individual person's laptop when that person remembers to run it?
- keybored 3y ago
  Like most things.
  - OJFord 3y ago
    But the whole point is not to have to do that. What you're asking for is basically just `npm upgrade` or `cargo upgrade` or whatever? The point of Renovate, Dependabot etc. is exactly the automated/scheduled running of those package manager updates.
    - keybored 3y ago
      Sigh. The answer to why they are this way is that it’s the whole point that they are this way.
      - OJFord 3y ago
        Well yes? You're complaining that a motorbike has an engine when you're perfectly capable of and would rather power it with your own two legs.
        keybored 3y ago
        What a great comparison.
zer00eyz 3y ago
A PR is easy to automate, hook into, an preserves ownership of the commit. Yes it bypasses YOUR workflow, but a PR works for everyone who uses GitHub. If you want something else that works for everyone who uses GitHub it's an issue, or an email with a patch file. Why a patch file. DO you want to own the change the bot suggested? There are a lot of orgs where the ownership matters more than the linting. You could just make the change yourself, sure, and then run it through your normal workflow... then your the author and commuter of the change...
- keybored 3y ago
  I stepped into the wrong workflow synagogue it seems.