STACKITGit/cli
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(cache delete): explain different API responses

Browse source 
Signed-off-by: Babak K. Shandiz <babakks@github.com>
This commit is contained in:
Babak K. Shandiz 2025-08-28 11:05:28 +01:00
parent d457a1bce0
commit 02d50700b5
No known key found for this signature in database
GPG key ID: 9472CAEFF56C742E
1 changed files with 12 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
pkg/cmd/cache/delete/delete.go vendored
View file

@ -167,6 +167,18 @@ func deleteCaches(opts *DeleteOptions, client *api.Client, repo ghrepo.Interface
base := fmt.Sprintf("repos/%s/actions/caches", repoName)
for _, cache := range toDelete {
// TODO(babakks): We use two different endpoints here which have different
// response schemas:
//
// 1. /repos/OWNER/REPO/actions/caches/ID (for deleting by cache ID)
// - returns HTTP 204 (NO CONTENT) on success
// 2. /repos/OWNER/REPO/actions/caches?key=KEY[&ref=REF] (for deleting by cache key, and optionally a ref)
// - returns HTTP 200 on success including information about the deleted caches
//
// So, if/when we decided to use the data in the response body we need
// to be careful with parsing. Probably want to split these API calls
// into separate functions.
path := ""
if id, ok := parseCacheID(cache); ok {
path = fmt.Sprintf("%s/%d", base, id)