feat: create automated dashboard ci #171
Conversation
✒️ PR Title Commitlint - ✔️ Lint success! |
| }, | ||
| repos: edges { | ||
| node { | ||
| ... on Repository { |
There was a problem hiding this comment.
What's this ... on Repository { part doing? Not familiar with the syntax.
There was a problem hiding this comment.
It forces graphql to make sure that the node is the correct type iirc, it also has other functions in graphql depending on how you use it, on line 103 I think it helps expand the response and acts like a for loop while if used in other places it can make blocks reusable: https://graphql.org/learn/queries/#fragments
| } | ||
| items: edges { | ||
| node { | ||
| id |
There was a problem hiding this comment.
Can we filter the query for what to remove to look for things closed or merged more than X days ago?
There was a problem hiding this comment.
Maybe though what I'm grabbing now is just 'everything on the board'
There was a problem hiding this comment.
How long are we talking days wise?
There was a problem hiding this comment.
Nvm - this doesn't look possible, you can find the type (issue/pr etc) but not any further details and the only option I can see as to ordering is the order it appears on the project board itself
| } | ||
| PRs: edges { | ||
| node { | ||
| id |
There was a problem hiding this comment.
Can we limit it to only authored by marvin-serp-bot (by variable).
There was a problem hiding this comment.
You can't limit by author unfortunately - it was one of the first things I tried to do
🚧 Suggest a change
A clear and concise description of what you are changing.
📝 Pre-merge checklist
Ready to merge? Do not merge until all checks are satisfied.
requiredCI checks passed on the most recent commit?type(scope): summarybreaking changesdeclared in the PR title in conventional-commit style? ie.type!(scope): summary