norman-abramovitz commented 3 weeks ago

I am using this issue as my scratch pad before making my PR.

Have releases show there actual locations
Show or remove releases that have been archived or abandoned
I will include my tooling in case people want to automate this in the future.
TODO want to find dates of things like archive date

Results of research

norman-abramovitz commented 3 weeks ago

tooling yq, jq, bash, gh, sort

for a in $(yq '.[]|.url' index.yml) do gh repo view "$a" --json url,isArchived,visibility | jq --arg indexUrl "$a" '.+=$ARGS.named' done | jq -f checker.jq | sort

norman-abramovitz commented 3 weeks ago

checker.jq script that produced the results above and used in the previous script.

def relevant(e): if e.isArchived then if e.indexUrl == e.url then "03 ARCHIVED " + "URL OK " + e.url else "02 ARCHIVED " + "URL CHANGE FROM " + e.indexUrl + " TO " + e.url end else if e.indexUrl != e.url then "01 ACTIVE " + "URL CHANGE FROM " + e.indexUrl + " TO " + e.url else "04 ACTIVE " + "URL OK " + e.url end end ;

relevant(.)

norman-abramovitz commented 3 weeks ago

to get. tags and archive date, It looks like I need to use REST or GraphQL since the data does not look available in the gh cli interface. So back to the drawing board.

norman-abramovitz commented 3 weeks ago

Not getting the latest tags yet, but got the other information that I could not get through gh repo view command.

This particular repo has tags that have no releases. Like 1.63 exists, but I am seeing 1.19 as my first tag. query { repository(owner: "bosh-packages", name: "cf-cli-release", followRenames: true) { name nameWithOwner owner { login } archivedAt isArchived updatedAt visibility url latestRelease { publishedAt tagName name } refs(refPrefix: "refs/tags/", last: 50) { nodes { repository { releases(last: 20, orderBy: {field: CREATED_AT, direction: DESC} ) { nodes { name createdAt url } } } } } } }

norman-abramovitz commented 3 weeks ago

Good thing I had some sleep, Since I am sorting descending, I want the first set of ref tags and not the last group. Sorting by date. Since I am looking for any activity it does not matter how tags are maintained as long as something is 'recent'.

Since some repos do not produce releases, I am looking at tags as way to tell if activity. releases are tagged so I am covering both cases by looking at tags.

norman-abramovitz commented 3 weeks ago

simplified query

{ repository(owner: "bosh-packages", name: "cf-cli-release", followRenames: true) { name nameWithOwner owner { login } archivedAt isArchived updatedAt visibility url latestRelease { publishedAt tagName name } refs( refPrefix: "refs/tags/" first: 20 orderBy: {field: TAG_COMMIT_DATE, direction: DESC} ) { edges { node { name } } } } }

Still want to see if I get more tag information out. I have not been successful figuring out the tag {} fragment yet.

Docs and explorer are not agreeing at the moment in my mind map.

norman-abramovitz commented 3 weeks ago

Looking better for automation purposes Looking to see if outer joins exists query { repository(owner: "bosh-packages", name: "cf-cli-release", followRenames: true) { name nameWithOwner owner { login } archivedAt isArchived updatedAt visibility url latestRelease { publishedAt tagName name } refs( refPrefix: "refs/tags/" first: 20 orderBy: {field: TAG_COMMIT_DATE, direction: DESC} ) { nodes { name id target { ... on Commit { commitMessage: message committedDate } } } } } }

norman-abramovitz commented 3 weeks ago

Adding arguments

query GetTags($owner: String!, $repo: String!) {
  repository(owner: $owner, name: $repo, followRenames: true) {
    name
    nameWithOwner
    owner {
      login
    }
    archivedAt
    isArchived
    updatedAt
    visibility
    url
    latestRelease {
      publishedAt
      tagName
      name
    }
    refs(
      refPrefix: "refs/tags/"
      first: 20
      orderBy: {field: TAG_COMMIT_DATE, direction: DESC}
    ) {
      nodes {
        name
        id
        target {
          ... on Commit {
            commitMessage: message
            committedDate
          }
        }
      }
    }
  }
}

The variables section that I will generate from the index.yml file { "owner": "bosh-packages", "repo": "cf-cli-release" }

cloudfoundry / bosh-io-releases

clean up bosh.io releases #117

tooling yq, jq, bash, gh, sort

checker.jq script that produced the results above and used in the previous script.

simplified query

Still want to see if I get more tag information out. I have not been successful figuring out the tag {} fragment yet.

Docs and explorer are not agreeing at the moment in my mind map.

Adding arguments