Reset history for version 2 about trealla HOT 23 OPEN

from trealla.

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

from trealla.

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

from trealla.

from trealla.

from trealla.

Maybe some junk got in there somehow, somewhere.

from trealla.

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

from trealla.

git gc?

from trealla.

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

from trealla.

from trealla.

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)

from trealla.

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

from trealla.

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?

from trealla.

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.

from trealla.

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.

from trealla.

from trealla.

https://sfconservancy.org/GiveUpGitHub/

from trealla.

from trealla.

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/

from trealla.

In any case, all the issues are lost.

from trealla.

It seems there are ways to recover issues.

from trealla.

@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.

from trealla.

from trealla.