Snapshots commit id not updated

[Thad Guidry]

Hmm, it looks like we are not actually taking advantage of the commit id being updated by the uploader... it continually uses the same old commit id that Antonin used on the initial creation of the uploader.  See below with Commit: 8c05e55

I would be nice to be able to click on it for any snapshot and see the real commit that generated the snapshot.

Instead, I always have to find the commit manually, for example the below one just now with the "g6283328" which is really SHA "6283328xxxxxx..."

Thoughts on improving that in our CI/CD setups?

Or am I doing something wrong and there's an easier method to get to the right commit, either on GitHub or somehow through my IDE?

Thad

https://www.linkedin.com/in/thadguidry/

https://calendly.com/thadguidry/

On Wed, Feb 3, 2021 at 2:49 PM openrefine-snapshot-uploader <notifi...@github.com> wrote:

OpenRefine snapshot 3.4-beta-835-g6283328-dirty

Repository: OpenRefine/OpenRefine-snapshot-releases · Tag: 3.4-beta-835-g6283328-dirty · Commit: 8c05e55 · Released by: openrefine-snapshot-uploader

This is a snapshot of the development version of OpenRefine, made on Wed Feb 3 20:49:38 2021.

This contains the latest new features and bug fixes, but might not have been tested as thoroughly as official releases.

Make sure you back up your workspace to avoid data loss and report any issues found with this version on the mailing list.

—

This release has 5 assets:

• openrefine-linux-3.4-beta-835-g6283328-dirty.tar.gz
• openrefine-mac-3.4-beta-835-g6283328-dirty.dmg
• openrefine-win-3.4-beta-835-g6283328-dirty.zip
• Source code (zip)
• Source code (tar.gz)

Visit the release page to download them.

—
You are receiving this because you are watching this repository.
View it on GitHub or unsubscribe from all notifications for this repository.

[Antonin Delpeuch (lists)]

We have had this discussion before: this commit id is that of the latest
commit in the OpenRefine-snapshot-releases repository, which is
unrelated to the latest commit in the OpenRefine repository.

Antonin

On 03/02/2021 22:13, Thad Guidry wrote:
> Hmm, it looks like we are not actually taking advantage of the commit id
> being updated by the uploader... it continually uses the same old commit
> id that Antonin used on the initial creation of the uploader.  See below
> with Commit: 8c05e55

> <https://github.com/OpenRefine/OpenRefine-snapshot-releases/commit/8c05e55d1c10938e2010c41693be985c5cca254f>

>
>
> I would be nice to be able to click on it for any snapshot and see the
> real commit that generated the snapshot.
> Instead, I always have to find the commit manually, for example the
> below one just now with the "g6283328" which is really SHA
> "6283328xxxxxx..."
>
> Thoughts on improving that in our CI/CD setups?
> Or am I doing something wrong and there's an easier method to get to the
> right commit, either on GitHub or somehow through my IDE?
>
> Thad
> https://www.linkedin.com/in/thadguidry/

> <https://www.linkedin.com/in/thadguidry/>
> https://calendly.com/thadguidry/ <https://calendly.com/thadguidry/>

>
>
> On Wed, Feb 3, 2021 at 2:49 PM openrefine-snapshot-uploader
> <notifi...@github.com <mailto:notifi...@github.com>> wrote:
>
>
> OpenRefine snapshot 3.4-beta-835-g6283328-dirty

> <https://github.com/OpenRefine/OpenRefine-snapshot-releases/releases/tag/3.4-beta-835-g6283328-dirty>
>
> Repository: OpenRefine/OpenRefine-snapshot-releases
> <https://github.com/OpenRefine/OpenRefine-snapshot-releases> · Tag:
> 3.4-beta-835-g6283328-dirty
> <https://github.com/OpenRefine/OpenRefine-snapshot-releases/tree/3.4-beta-835-g6283328-dirty>
> · Commit: 8c05e55
> <https://github.com/OpenRefine/OpenRefine-snapshot-releases/commit/8c05e55d1c10938e2010c41693be985c5cca254f>
> · Released by: openrefine-snapshot-uploader
> <https://github.com/openrefine-snapshot-uploader>

>
> This is a snapshot of the development version of OpenRefine, made on
> Wed Feb 3 20:49:38 2021.
>
> This contains the latest new features and bug fixes, but might not
> have been tested as thoroughly as official releases.
>
> Make sure you back up your workspace

> <https://docs.openrefine.org/manual/installing#back-up-your-data> to

> avoid data loss and report any issues found with this version on the

> mailing list <https://groups.google.com/forum/#!forum/openrefine>.
>
> —

>
> This release has 5 assets:
>

> * openrefine-linux-3.4-beta-835-g6283328-dirty.tar.gz
> * openrefine-mac-3.4-beta-835-g6283328-dirty.dmg
> * openrefine-win-3.4-beta-835-g6283328-dirty.zip
> * Source code (zip)
> * Source code (tar.gz)
>
> Visit the release page
> <https://github.com/OpenRefine/OpenRefine-snapshot-releases/releases/tag/3.4-beta-835-g6283328-dirty>

> to download them.
>
> —
> You are receiving this because you are watching this repository.
> View it on GitHub

> <https://github.com/OpenRefine/OpenRefine-snapshot-releases/releases/tag/3.4-beta-835-g6283328-dirty>
> or unsubscribe
> <https://github.com/OpenRefine/OpenRefine-snapshot-releases/unsubscribe_via_email/AAHQ2RUF5KH7TP4K7NVX3D3S5GZHJANCNFSM4DQY6BDQ>

> from all notifications for this repository.
>

> --
> You received this message because you are subscribed to the Google
> Groups "OpenRefine Development" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to openrefine-de...@googlegroups.com
> <mailto:openrefine-de...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/openrefine-dev/CAChbWaPFR40Swyc7VsyQHk2f_CcGx13_T0jicoqy%3DFYT%2BkZK-w%40mail.gmail.com
> <https://groups.google.com/d/msgid/openrefine-dev/CAChbWaPFR40Swyc7VsyQHk2f_CcGx13_T0jicoqy%3DFYT%2BkZK-w%40mail.gmail.com?utm_medium=email&utm_source=footer>.