Re: Automatic updates?
It took me some googling... I had forgotten about that step. Great news. Thank you! On Thu, May 19, 2022 at 12:27 PM Tilman Hausherr wrote: > Am 19.05.2022 um 18:16 schrieb Tim Allison: > > Hmmm... what do you see here: https://gitbox.apache.org/boxer/ > > Thank you, I hadn't known about that. I have now linked my account. The > appearance of > > https://github.com/apache/tika/pull/561/ > > has now changed, cool! > > Tilman > > > > > > > On Thu, May 19, 2022 at 11:58 AM Tilman Hausherr > > wrote: > > > >> I'm unable to show it now, but I never had a "merge" button. But I > >> remember a "Only those with write access to this repository can merge > >> pull requests" text, could it be that I need some additional > permissions? > >> > >> Tilman > >> > >> Am 19.05.2022 um 14:00 schrieb Tim Allison: > >>> I just click the button. Is your username asfgit? Kidding! I have no > >>> idea why your name isn't showing up. > >>> > >>> On Thu, May 19, 2022 at 12:03 AM Tilman Hausherr > > >>> wrote: > >>> > What do you do differently than I do? I noticed that in the recent > commit, your name appears in the PR, mine doesn't. > > https://github.com/apache/tika/pull/562/ > https://github.com/apache/tika/pull/563/ > "asfgit" > > https://github.com/apache/tika/pull/564/ > "tballison" > > Could it because I'm using my real mail address in commits and you're > using your apache mail address? > > Tilman > >> > >
Re: Automatic updates?
Am 19.05.2022 um 18:16 schrieb Tim Allison: Hmmm... what do you see here: https://gitbox.apache.org/boxer/ Thank you, I hadn't known about that. I have now linked my account. The appearance of https://github.com/apache/tika/pull/561/ has now changed, cool! Tilman On Thu, May 19, 2022 at 11:58 AM Tilman Hausherr wrote: I'm unable to show it now, but I never had a "merge" button. But I remember a "Only those with write access to this repository can merge pull requests" text, could it be that I need some additional permissions? Tilman Am 19.05.2022 um 14:00 schrieb Tim Allison: I just click the button. Is your username asfgit? Kidding! I have no idea why your name isn't showing up. On Thu, May 19, 2022 at 12:03 AM Tilman Hausherr wrote: What do you do differently than I do? I noticed that in the recent commit, your name appears in the PR, mine doesn't. https://github.com/apache/tika/pull/562/ https://github.com/apache/tika/pull/563/ "asfgit" https://github.com/apache/tika/pull/564/ "tballison" Could it because I'm using my real mail address in commits and you're using your apache mail address? Tilman
Re: Automatic updates?
Hmmm... what do you see here: https://gitbox.apache.org/boxer/ On Thu, May 19, 2022 at 11:58 AM Tilman Hausherr wrote: > I'm unable to show it now, but I never had a "merge" button. But I > remember a "Only those with write access to this repository can merge > pull requests" text, could it be that I need some additional permissions? > > Tilman > > Am 19.05.2022 um 14:00 schrieb Tim Allison: > > I just click the button. Is your username asfgit? Kidding! I have no > > idea why your name isn't showing up. > > > > On Thu, May 19, 2022 at 12:03 AM Tilman Hausherr > > wrote: > > > >> What do you do differently than I do? I noticed that in the recent > >> commit, your name appears in the PR, mine doesn't. > >> > >> https://github.com/apache/tika/pull/562/ > >> https://github.com/apache/tika/pull/563/ > >> "asfgit" > >> > >> https://github.com/apache/tika/pull/564/ > >> "tballison" > >> > >> Could it because I'm using my real mail address in commits and you're > >> using your apache mail address? > >> > >> Tilman > >
Re: Automatic updates?
I'm unable to show it now, but I never had a "merge" button. But I remember a "Only those with write access to this repository can merge pull requests" text, could it be that I need some additional permissions? Tilman Am 19.05.2022 um 14:00 schrieb Tim Allison: I just click the button. Is your username asfgit? Kidding! I have no idea why your name isn't showing up. On Thu, May 19, 2022 at 12:03 AM Tilman Hausherr wrote: What do you do differently than I do? I noticed that in the recent commit, your name appears in the PR, mine doesn't. https://github.com/apache/tika/pull/562/ https://github.com/apache/tika/pull/563/ "asfgit" https://github.com/apache/tika/pull/564/ "tballison" Could it because I'm using my real mail address in commits and you're using your apache mail address? Tilman
Re: Automatic updates?
I just click the button. Is your username asfgit? Kidding! I have no
idea why your name isn't showing up.
On Thu, May 19, 2022 at 12:03 AM Tilman Hausherr
wrote:
> What do you do differently than I do? I noticed that in the recent
> commit, your name appears in the PR, mine doesn't.
>
> https://github.com/apache/tika/pull/562/
> https://github.com/apache/tika/pull/563/
> "asfgit"
>
> https://github.com/apache/tika/pull/564/
> "tballison"
>
> Could it because I'm using my real mail address in commits and you're
> using your apache mail address?
>
> Tilman
>
> Am 18.05.2022 um 15:36 schrieb Tim Allison:
> > Oh, ok, phew. Thank you, Tilman. I remember seeing you merge some of
> the
> > others, and I agree, I'm not able to see that history now.
> >
> > As long as our AI overlords haven't taken control of our code without
> some
> > kind of manual review, all good. Thank you.
> >
> > On Wed, May 18, 2022 at 8:37 AM Tilman Hausherr
> > wrote:
> >
> >> The previous one (not this one) was me, I merged the branch locally and
> >> then pushed it.
> >>
> >> So there's still a manual step but somehow the history doesn't show
> this.
> >>
> >> Tilman
> >>
> >>
> >>
> >> --- Original-Nachricht ---
> >> Von: Tim Allison
> >> Betreff: Automatic updates?
> >> Datum: 18. Mai 2022, 14:25
> >> An:
> >>
> >>
> >>
> >>
> >> @font-face { font-family: telegrotesk-medium_normal; src:
> >> url("file:///android_asset/fonts/telegrotesk_normal.ttf");}html,body {
> >> font-family: "telegrotesk-medium_normal"; font-size: medium; color:
> >> #4b4b4b; width: 100%;}
> >>
> >> All,
> >> It feels like something changed in the last week with our dependabot
> >> integration. We used to get PRs. Now we're getting PRs that are
> >> automatically merged.
> >> I don't think this is a great idea. What do you think?
> >>
> >> Best,
> >>
> >> Tim
> >>
> >> On Wed, May 18, 2022 at 1:55 AM GitBox wrote:
> >>
> >>> dependabot[bot] opened a new pull request, #562:
> >>> URL: https://github.com/apache/tika/pull/562
> >>>
> >>> Bumps [zstd-jni](https://github.com/luben/zstd-jni) from 1.5.2-2 to
> >>> 1.5.2-3.
> >>>
> >>> Commits
> >>>
> >>> https://github.com/luben/zstd-jni/commit/c983ae3e086b63a40e1bb430cb2ebf95ecc52c71
> >> ">c983ae3;
> >>> Adjust signature comments after
> >>> e5c6a3290b8335db7c70877fda22ca26a96c72e4.
> >>> https://github.com/luben/zstd-jni/commit/510bbd6be80592227c6e5cf8cd8d71cb76c0c279
> >> ">510bbd6;
> >>> Add methods for streaming (de)compression of direct ByteBuffers.
> >>> https://github.com/luben/zstd-jni/commit/62b9dad49fc00f253cb35c1942c3ca6af4ee2b47
> >> ">62b9dad;
> >>> Fix lgtm C++.
> >>> https://github.com/luben/zstd-jni/commit/73ae46e1af16619143b7c87e35ad9c05363e2c97
> >> ">73ae46e;
> >>> v1.5.2-3
> >>> https://github.com/luben/zstd-jni/commit/e5c6a3290b8335db7c70877fda22ca26a96c72e4
> >> ">e5c6a32;
> >>> Fix overflows
> >>> https://github.com/luben/zstd-jni/commit/54d3d50c16d96bd8a30e2d4c0a9648001a52d6f9
> >> ">54d3d50;
> >>> Fix some error return codes.
> >>> https://github.com/luben/zstd-jni/commit/b788a2ed7a5e36e5252b1696e6cc8bae48a7afbc
> >> ">b788a2e;
> >>> Upgrade scala.
> >>> https://github.com/luben/zstd-jni/commit/31060934c26e080031465702ec369591e12874f8
> >> ">3106093;
> >>> Add NoFinalizer variants for the direct buffer streams.
> >>> See full diff in https://github.com/luben/zstd-jni/compare/v1.5.2-2...v1.5.2-3;>compare
> >>> view
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores
> >>> )
> >>>
> >>> Dependabot will resolve any conflicts with this PR as long as you don't
> >>> alter it yourself. You can also trigger a rebase manually by commenting
> >>> `@dependabot rebase`.
> >>>
> >>> [//]: # (dependabot-automerge-start)
> >>> [//]: # (dependabot-automerge-end)
> >>>
> >>> ---
> >>>
> >>>
> >>> Dependabot commands and options
> >>>
> >>>
> >>> You can trigger Dependabot actions by commenting on this PR:
> >>> - `@dependabot rebase` will rebase this PR
> >>> - `@dependabot recreate` will recreate this PR, overwriting any edits
> >>> that have been made to it
> >>> - `@dependabot merge` will merge this PR after your CI passes on it
> >>> - `@dependabot squash and merge` will squash and merge this PR after
> >>> your CI passes on it
> >>> - `@dependabot cancel merge` will cancel a previously requested merge
> >>> and block automerging
> >>> - `@dependabot reopen` will reopen this PR if it is closed
> >>> - `@dependabot close` will close this PR and stop Dependabot recreating
> >>> it. You can achieve the same result by closing it manually
> >>> - `@dependabot ignore this major version` will close this PR and stop
> >>> Dependabot creating any more for this major version (unless you reopen
> >> the
>
Re: Automatic updates?
What do you do differently than I do? I noticed that in the recent
commit, your name appears in the PR, mine doesn't.
https://github.com/apache/tika/pull/562/
https://github.com/apache/tika/pull/563/
"asfgit"
https://github.com/apache/tika/pull/564/
"tballison"
Could it because I'm using my real mail address in commits and you're
using your apache mail address?
Tilman
Am 18.05.2022 um 15:36 schrieb Tim Allison:
Oh, ok, phew. Thank you, Tilman. I remember seeing you merge some of the
others, and I agree, I'm not able to see that history now.
As long as our AI overlords haven't taken control of our code without some
kind of manual review, all good. Thank you.
On Wed, May 18, 2022 at 8:37 AM Tilman Hausherr
wrote:
The previous one (not this one) was me, I merged the branch locally and
then pushed it.
So there's still a manual step but somehow the history doesn't show this.
Tilman
--- Original-Nachricht ---
Von: Tim Allison
Betreff: Automatic updates?
Datum: 18. Mai 2022, 14:25
An:
@font-face { font-family: telegrotesk-medium_normal; src:
url("file:///android_asset/fonts/telegrotesk_normal.ttf");}html,body {
font-family: "telegrotesk-medium_normal"; font-size: medium; color:
#4b4b4b; width: 100%;}
All,
It feels like something changed in the last week with our dependabot
integration. We used to get PRs. Now we're getting PRs that are
automatically merged.
I don't think this is a great idea. What do you think?
Best,
Tim
On Wed, May 18, 2022 at 1:55 AM GitBox wrote:
dependabot[bot] opened a new pull request, #562:
URL: https://github.com/apache/tika/pull/562
Bumps [zstd-jni](https://github.com/luben/zstd-jni) from 1.5.2-2 to
1.5.2-3.
Commits
https://github.com/luben/zstd-jni/commit/c983ae3e086b63a40e1bb430cb2ebf95ecc52c71
">c983ae3;
Adjust signature comments after
e5c6a3290b8335db7c70877fda22ca26a96c72e4.
https://github.com/luben/zstd-jni/commit/510bbd6be80592227c6e5cf8cd8d71cb76c0c279
">510bbd6;
Add methods for streaming (de)compression of direct ByteBuffers.
https://github.com/luben/zstd-jni/commit/62b9dad49fc00f253cb35c1942c3ca6af4ee2b47
">62b9dad;
Fix lgtm C++.
https://github.com/luben/zstd-jni/commit/73ae46e1af16619143b7c87e35ad9c05363e2c97
">73ae46e;
v1.5.2-3
https://github.com/luben/zstd-jni/commit/e5c6a3290b8335db7c70877fda22ca26a96c72e4
">e5c6a32;
Fix overflows
https://github.com/luben/zstd-jni/commit/54d3d50c16d96bd8a30e2d4c0a9648001a52d6f9
">54d3d50;
Fix some error return codes.
https://github.com/luben/zstd-jni/commit/b788a2ed7a5e36e5252b1696e6cc8bae48a7afbc
">b788a2e;
Upgrade scala.
https://github.com/luben/zstd-jni/commit/31060934c26e080031465702ec369591e12874f8
">3106093;
Add NoFinalizer variants for the direct buffer streams.
See full diff in https://github.com/luben/zstd-jni/compare/v1.5.2-2...v1.5.2-3;>compare
view
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores
)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the
PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the
PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR
or upgrade to it yourself)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@tika.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: Automatic updates?
Oh, ok, phew. Thank you, Tilman. I remember seeing you merge some of the
others, and I agree, I'm not able to see that history now.
As long as our AI overlords haven't taken control of our code without some
kind of manual review, all good. Thank you.
On Wed, May 18, 2022 at 8:37 AM Tilman Hausherr
wrote:
> The previous one (not this one) was me, I merged the branch locally and
> then pushed it.
>
> So there's still a manual step but somehow the history doesn't show this.
>
> Tilman
>
>
>
> --- Original-Nachricht ---
> Von: Tim Allison
> Betreff: Automatic updates?
> Datum: 18. Mai 2022, 14:25
> An:
>
>
>
>
> @font-face { font-family: telegrotesk-medium_normal; src:
> url("file:///android_asset/fonts/telegrotesk_normal.ttf");}html,body {
> font-family: "telegrotesk-medium_normal"; font-size: medium; color:
> #4b4b4b; width: 100%;}
>
> All,
> It feels like something changed in the last week with our dependabot
> integration. We used to get PRs. Now we're getting PRs that are
> automatically merged.
> I don't think this is a great idea. What do you think?
>
> Best,
>
> Tim
>
> On Wed, May 18, 2022 at 1:55 AM GitBox wrote:
>
> >
> > dependabot[bot] opened a new pull request, #562:
> > URL: https://github.com/apache/tika/pull/562
> >
> > Bumps [zstd-jni](https://github.com/luben/zstd-jni) from 1.5.2-2 to
> > 1.5.2-3.
> >
> > Commits
> >
> > https://github.com/luben/zstd-jni/commit/c983ae3e086b63a40e1bb430cb2ebf95ecc52c71
> ">c983ae3;
> > Adjust signature comments after
> > e5c6a3290b8335db7c70877fda22ca26a96c72e4.
> > https://github.com/luben/zstd-jni/commit/510bbd6be80592227c6e5cf8cd8d71cb76c0c279
> ">510bbd6;
> > Add methods for streaming (de)compression of direct ByteBuffers.
> > https://github.com/luben/zstd-jni/commit/62b9dad49fc00f253cb35c1942c3ca6af4ee2b47
> ">62b9dad;
> > Fix lgtm C++.
> > https://github.com/luben/zstd-jni/commit/73ae46e1af16619143b7c87e35ad9c05363e2c97
> ">73ae46e;
> > v1.5.2-3
> > https://github.com/luben/zstd-jni/commit/e5c6a3290b8335db7c70877fda22ca26a96c72e4
> ">e5c6a32;
> > Fix overflows
> > https://github.com/luben/zstd-jni/commit/54d3d50c16d96bd8a30e2d4c0a9648001a52d6f9
> ">54d3d50;
> > Fix some error return codes.
> > https://github.com/luben/zstd-jni/commit/b788a2ed7a5e36e5252b1696e6cc8bae48a7afbc
> ">b788a2e;
> > Upgrade scala.
> > https://github.com/luben/zstd-jni/commit/31060934c26e080031465702ec369591e12874f8
> ">3106093;
> > Add NoFinalizer variants for the direct buffer streams.
> > See full diff in https://github.com/luben/zstd-jni/compare/v1.5.2-2...v1.5.2-3;>compare
> > view
> >
> >
> >
> >
> >
> > [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores
> > )
> >
> > Dependabot will resolve any conflicts with this PR as long as you don't
> > alter it yourself. You can also trigger a rebase manually by commenting
> > `@dependabot rebase`.
> >
> > [//]: # (dependabot-automerge-start)
> > [//]: # (dependabot-automerge-end)
> >
> > ---
> >
> >
> > Dependabot commands and options
> >
> >
> > You can trigger Dependabot actions by commenting on this PR:
> > - `@dependabot rebase` will rebase this PR
> > - `@dependabot recreate` will recreate this PR, overwriting any edits
> > that have been made to it
> > - `@dependabot merge` will merge this PR after your CI passes on it
> > - `@dependabot squash and merge` will squash and merge this PR after
> > your CI passes on it
> > - `@dependabot cancel merge` will cancel a previously requested merge
> > and block automerging
> > - `@dependabot reopen` will reopen this PR if it is closed
> > - `@dependabot close` will close this PR and stop Dependabot recreating
> > it. You can achieve the same result by closing it manually
> > - `@dependabot ignore this major version` will close this PR and stop
> > Dependabot creating any more for this major version (unless you reopen
> the
> > PR or upgrade to it yourself)
> > - `@dependabot ignore this minor version` will close this PR and stop
> > Dependabot creating any more for this minor version (unless you reopen
> the
> > PR or upgrade to it yourself)
> > - `@dependabot ignore this dependency` will close this PR and stop
> > Dependabot creating any more for this dependency (unless you reopen the
> PR
> > or upgrade to it yourself)
> >
> >
> >
> >
> >
> > --
> > This is an automated message from the Apache Git Service.
> > To respond to the message, please log on to GitHub and use the
> > URL above to go to the specific comment.
> >
> > To unsubscribe, e-mail: dev-unsubscr...@tika.apache.org
> >
> > For queries about this service, please contact Infrastructure at:
> > us...@infra.apache.org
> >
> >
>
>
