What's Changed

• Handle latest upload by @tanho63 in https://github.com/ropensci/piggyback/pull/86
• Add GHA for codecov by @tanho63 in https://github.com/ropensci/piggyback/pull/87
• make pb_list() respect option "piggyback.verbose" by @mrcaseb in https://github.com/ropensci/piggyback/pull/91
• pb_download properly passes token to subfunctions by @tanho63 in https://github.com/ropensci/piggyback/pull/89
• Update pb_upload.R by @tanho63 in https://github.com/ropensci/piggyback/pull/94
• pb_release_create warn instead of error if release already exists by @tanho63 in https://github.com/ropensci/piggyback/pull/96
• Fix mismatching backtick by @agila5 in https://github.com/ropensci/piggyback/pull/99
• fixup test failures by @tanho63 in https://github.com/ropensci/piggyback/pull/102
• more updates by @tanho63 in https://github.com/ropensci/piggyback/pull/103

New Contributors

• @agila5 made their first contribution in https://github.com/ropensci/piggyback/pull/99

Full Changelog: https://github.com/ropensci/piggyback/compare/v0.1.4...v0.1.5

What's Changed

• Change default of show_progress to interactive() by @mrcaseb in https://github.com/ropensci/piggyback/pull/74
• handle empty tokens from gh::gh_token, resolves #77 by @tanho63 in https://github.com/ropensci/piggyback/pull/78
• fix bug in auth header by @tanho63 in https://github.com/ropensci/piggyback/pull/79
• simplify guess repo, closes #80 by @tanho63 in https://github.com/ropensci/piggyback/pull/82
• pb_release_delete + testing revamp by @tanho63 in https://github.com/ropensci/piggyback/pull/85

Full Changelog: https://github.com/ropensci/piggyback/compare/v0.1.3...v0.1.4

What's Changed

• Fix upload for releases with no existing assets by @tanho63 in https://github.com/ropensci/piggyback/pull/68
• Data frame subsetting works if tibble is not installed (closes #70). by @PMassicotte in https://github.com/ropensci/piggyback/pull/71

New Contributors

• @PMassicotte made their first contribution in https://github.com/ropensci/piggyback/pull/71

Full Changelog: https://github.com/ropensci/piggyback/compare/v0.1.2...v0.1.3

What's Changed

• fixup intro vignette to remove track/push/pull mentions by @tanho63 in https://github.com/ropensci/piggyback/pull/53
• Fix upload dir argument and cleanup intro vignette by @tanho63 in https://github.com/ropensci/piggyback/pull/56
• fix use_timestamps in pb_upload by @tanho63 in https://github.com/ropensci/piggyback/pull/57
• new release errors reported verbosely by @tanho63 in https://github.com/ropensci/piggyback/pull/59
• Refactoring of pb_list() and other changes by @tanho63 in https://github.com/ropensci/piggyback/pull/65
• Use verbose option by @tanho63 in https://github.com/ropensci/piggyback/pull/66

Full Changelog: https://github.com/ropensci/piggyback/compare/v0.1.1...v0.1.2

What's Changed

• Rely on gh::gh_token() for credential management by @cboettig in https://github.com/ropensci/piggyback/pull/50

Full Changelog: https://github.com/ropensci/piggyback/compare/v0.1.0...v0.1.1

• address remaining authentication issue in changes to GitHub API (on pb_upload()) [#47]
• Use flat file structure on upload/download instead of encoding path [#48]
• improve performance via more aggressive memoising of pb_info() calls, inceasing default piggyback_cache_duration to 10 minutes [#46]
• Resolve bug introduced by API changes that would stop creation of tags on repos with default branch called main or without previous releases [#48]

Data release

Changelog: v0.0.10

• Improve interface for specifying when to overwrite files on upload (#25)
• Bugfixes for errors introduced in v0.0.9:
  • Uploading of directory paths could cause download errors in pb_download(). (#24)
  • Access all assets on a release instead of first 30. This could break upload and download. (#23, #24)

Changelog: v0.0.9

• Enable re-upload and deletion of partially uploaded files (#19)

Changelog: v0.0.8

• Updates to documentation, streamlining tests
• remove dependency on utils::askYesNo which is only available in R >= 3.5.0

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.

Changelog: v0.0.7

• Initial release to CRAN

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.

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.

Data release

Data release

Data release