Reset history for version 2

[infradig]

Time for a clean slate after two years of code-cruft. A gigabyte of git commit history was just ridiculous.

[infradig]

I will restore the old repo though in a while, for reference purposes.

[pabs3]

Hmm, I cloned a fork of the old repo and got 8MB and 7448 commits. Where does the 1GB come from?

[infradig]

Probably because it's only main. 99% of work happened in devel or other specialist branches.

On Tue, Aug 9, 2022 at 11:06 AM Paul Wise @.***> wrote:

Hmm, I cloned a fork of the old repo https://github.com/guregu/trealla and got 8MB and 7448 commits. Where does the 1GB come from?

— Reply to this email directly, view it on GitHub https://github.com/trealla-prolog/trealla/issues/1#issuecomment-1208775431, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFNKSETDOR3R5WBCAQHVJDLVYGVIZANCNFSM554DYNJA . You are receiving this because you authored the thread.Message ID: @.***>

[infradig]

[infradig]

Maybe some junk got in there somehow, somewhere.

[infradig]

It seems all the space is taken by many, many .pack files, the largest being 400MB.

[pmoura]

git gc?

[infradig]

Maybe would have worked, saw a lot of conflicting advice on that. Anyway I like a fresh bowl start, feels like a load off my back.

On Tue, Aug 9, 2022 at 6:22 PM Paulo Moura @.***> wrote:

git gc?

— Reply to this email directly, view it on GitHub https://github.com/trealla-prolog/trealla/issues/1#issuecomment-1209069428, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFNKSEVKW5WJZAHO2QEBDDDVYIINDANCNFSM554DYNJA . You are receiving this because you authored the thread.Message ID: @.***>

[flexoron]

Perhaps contains more than 3 million json files $ git rev-list --objects --all | grep .json | wc -l 3285524

For example: data/test-cases/e60dce80b7e4576f.json

Maybe avoidable

Decreased now (v2.0.1) $ git rev-list --objects --all | grep .json | grep test-cases | wc -l 16798

[infradig]

And I have no idea what they are.

On Tue, Aug 9, 2022 at 9:43 PM flexoron @.***> wrote:

Perhaps contains more than 3 million json files $ git rev-list --objects --all | grep .json | wc -l 3285524

For example: data/test-cases/e60dce80b7e4576f.json

Maybe avoidable

— Reply to this email directly, view it on GitHub https://github.com/trealla-prolog/trealla/issues/1#issuecomment-1209272599, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFNKSERXLAYBQCY5W5XCVDTVYI76XANCNFSM554DYNJA . You are receiving this because you authored the thread.Message ID: @.***>

[flexoron]

There is a trealla/.github/workflows/compliance.yml file which tries to generate an Allure-Report(whatever that is) Click Actions above (Code Issues Pull requests Actions Security Insights)

All workflows

Pages build and deployment by BOT 6 hours ago

Fix setof/3 to fail (like bagof/3) ... testing 13 hours ago

Initial commit ... testing yesterday

As you can see a BOT processes commits and fills up the gh-pages branch But don't ask me why it has been configured. Perhaps you can disable it in Settings/Pages (Repo configurations area)

[flexoron]

This workflows/compliance.yml file is an ansible 'script' and every time you push something into the 'testing' branch,later on a build process(an action) starts (somewhere on github I guess), but do you really need these runs? I assume this 'allure-report' generation creates all these files in the gh-pages directory.

https://github.com/peaceiris/actions-gh-pages Set a branch name to use as GitHub Pages branch. The default is gh-pages.

Also see/ask @pmoura: logtalk_allure_report

[flexoron]

Here are the json files:

Actions -> Fix setof/3 to fail (like bagof/3) -> compliance.yml on push -> test ->
Upload Allure Report -> Create a commit:

  /usr/bin/git commit -m deploy: 035aea994d7b215010b6c6d820d9b05382369b53
  Auto packing the repository in background for optimum performance.
  See "git help gc" for manual housekeeping.
  [gh-pages 11a0fef] deploy: 035aea994d7b215010b6c6d820d9b05382369b53
   16820 files changed, 721462 insertions(+), 721451 deletions(-)
  : 
  : 

Perhaps logtalk test results?

[pmoura]

In the old repo, Logtalk distribution tests (which include the Prolog standard compliance suite) were run when changes were pushed to the testing branch. The resulting report was published using GitHub Pages. Regularly pruning the history of the gh-pages would have avoided the perceived bloat in the gh-pages branch.

[UWN]

I will restore the old repo though in a while, for reference purposes.

This will not restore the cross-links with other projects AFAIK. They are just lost. So for the future, it does not make sense to contribute on your github pages.

[infradig]

These cross links are ephemeral anyway. I have for a while contemplated a move from Github, it's not what it used to be. But not yet.

On Wed, 10 Aug 2022, 04:49 UWN, @.***> wrote:

I will restore the old repo though in a while, for reference purposes.

This will not restore the cross-links with other projects AFAIK. They are just lost. So for the future, it does not make sense to contribute on your github pages.

— Reply to this email directly, view it on GitHub https://github.com/trealla-prolog/trealla/issues/1#issuecomment-1209753773, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFNKSESLNQ65RW4N5PICJUDVYKR2NANCNFSM554DYNJA . You are receiving this because you authored the thread.Message ID: @.***>

[flexoron]

https://sfconservancy.org/GiveUpGitHub/

[infradig]

Yes, I have never had a problem with hosting on a proprietary platform, but being owned and used by Microsoft I do find a problem. Gitlab is stand-alone and has certain advantages (such as familiarity). Other options might be worth looking into.

On Wed, Aug 10, 2022 at 8:50 AM flexoron @.***> wrote:

https://sfconservancy.org/GiveUpGitHub/

— Reply to this email directly, view it on GitHub https://github.com/trealla-prolog/trealla/issues/1#issuecomment-1209968589, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFNKSEQNAATABVHASENZNUDVYLOC7ANCNFSM554DYNJA . You are receiving this because you authored the thread.Message ID: @.***>

[flexoron]

Berlin,Berlin https://codeberg.org/ Amsterdam https://sourcehut.org/

btw Look at this: a sourcehut development. Really cool video, 4 minutes https://aerc-mail.org/

[UWN]

In any case, all the issues are lost.

[UWN]

It seems there are ways to recover issues.

[UWN]

@infragdig: According to a response from github, only the owner can restore a repository including their issues. And that within 90 days. So you would need to restore it somehow.

[infradig]

I've got a spare PI/4, and I could use that with Gitea 😎

On Wed, Aug 10, 2022 at 9:25 AM flexoron @.***> wrote:

Berlin,Berlin https://codeberg.org/ Amsterdam https://sourcehut.org/

— Reply to this email directly, view it on GitHub https://github.com/trealla-prolog/trealla/issues/1#issuecomment-1209989440, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFNKSEXMB5PTFJFUPIY4V5TVYLSHPANCNFSM554DYNJA . You are receiving this because you authored the thread.Message ID: @.***>