piggyback (Q92770)

From MaRDI portal
Managing Larger Data on a GitHub Repository
Language Label Description Also known as
English
piggyback
Managing Larger Data on a GitHub Repository

    Statements

    0.1.4
    19 July 2022
    0 references
    0.0.7
    30 September 2018
    0 references
    0.0.8
    6 October 2018
    0 references
    0.0.9
    9 January 2019
    0 references
    0.0.10
    7 February 2019
    0 references
    0.0.11
    25 February 2020
    0 references
    0.1.0
    6 August 2021
    0 references
    0.1.1
    9 September 2021
    0 references
    0.1.2
    27 April 2022
    0 references
    0.1.3
    19 May 2022
    0 references
    0.1.4
    20 July 2022
    0 references
    0.1.5
    10 July 2023
    0 references
    0 references
    0 references
    0 references
    10 July 2023
    0 references
    Because larger (> 50 MB) data files cannot easily be committed to git, a different approach is required to manage data associated with an analysis in a GitHub repository. This package provides a simple work-around by allowing larger (up to 2 GB) data files to piggyback on a repository as assets attached to individual GitHub releases. These files are not handled by git in any way, but instead are uploaded, downloaded, or edited directly by calls through the GitHub API. These data files can be versioned manually by creating different releases. This approach works equally well with public or private repositories. Data can be uploaded and downloaded programmatically from scripts. No authentication is required to download data from public repositories.
    0 references
    0 references
    0 references
    0 references
    0 references
    0 references
    0 references
    0 references
    0 references
    0 references
    0 references