repo-utils / org-labels Goto Github PK

I get the following error when trying to use this tool. I’m using macOS 12.0.1 on an Apple M1 Pro, using node v17.3.1.

 (node:91811) TimeoutOverflowWarning: 4294967296000 does not fit into a 32-bit signed integer.
Timer duration was truncated to 2147483647.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:91811) TimeoutOverflowWarning: 4294967296000 does not fit into a 32-bit signed integer.
Timer duration was truncated to 2147483647.
Error: Not Found
    at BufferList.afterCreateAuthResponse [as _callback] (/Users/Mark.Crossfield/.nvm/versions/node/v17.3.1/lib/node_modules/org-labels/node_modules/ghauth/ghauth.js:39:19)
    at BufferList.end (/Users/Mark.Crossfield/.nvm/versions/node/v17.3.1/lib/node_modules/org-labels/node_modules/bl/bl.js:75:10)
    at Stream.onend (node:internal/streams/legacy:47:10)
    at Stream.emit (node:events:402:35)
    at Stream.handleEnd (/Users/Mark.Crossfield/.nvm/versions/node/v17.3.1/lib/node_modules/org-labels/node_modules/duplexer/index.js:81:21)
    at Stream.emit (node:events:402:35)
    at drain (/Users/Mark.Crossfield/.nvm/versions/node/v17.3.1/lib/node_modules/org-labels/node_modules/through/index.js:33:23)
    at Stream.stream.queue.stream.push (/Users/Mark.Crossfield/.nvm/versions/node/v17.3.1/lib/node_modules/org-labels/node_modules/through/index.js:41:5)
    at Stream.end (/Users/Mark.Crossfield/.nvm/versions/node/v17.3.1/lib/node_modules/org-labels/node_modules/through/index.js:17:35)
    at _end (/Users/Mark.Crossfield/.nvm/versions/node/v17.3.1/lib/node_modules/org-labels/node_modules/through/index.js:61:9)
    at Stream.stream.end (/Users/Mark.Crossfield/.nvm/versions/node/v17.3.1/lib/node_modules/org-labels/node_modules/through/index.js:70:5)
    at IncomingMessage.onend (node:internal/streams/readable:716:10)
    at Object.onceWrapper (node:events:509:28)
    at IncomingMessage.emit (node:events:402:35)
    at endReadableNT (node:internal/streams/readable:1343:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

A lot of orgs have forks in their orgs, but it doesn't really make sense to manage labels on forks. There should be an option to skip forks.

In order to make it work with private org repos, it is necessary to use the orgs API (instead of the users API, which does not expose private org repos, even if the user has access and the access token is set up correctly). I was able to get it working using the following:

https://api.github.com/orgs/<org>/repos?page=<i>

after authenticating, the tool runs, spits out some random 404, and then makes no changes anywhere

$ org-labels remove trailsjs bug
GitHub rate limit remaining: 4845
found 26 repositories in trailsjs

Error: 404 - https://api.github.com/repos/trailsjs/badgeboard/labels/bug

if I make a get request in my browser for that label, I see it:

{
  "url": "https://api.github.com/repos/trailsjs/badgeboard/labels/bug",
  "name": "bug",
  "color": "fc2929"
}

Standardize currently adds all the labels from the JSON file and sets the color if the label is new. It doesn't update colors on existing tags though. That seems to go against the name of the action. It should be fully updating existing labels to match the standard.

btw: this project is saving me a ton of time. Thanks

Currently it only works for organizations, user support could also be good though.

I'm trying to use this and it appears to only be populating the labels in my public repos. I've updated the token to ensure it has the privilege. Can you confirm if this should work across private repos too?

GitHub rate limit remaining: 4933
found 30 repositories in ...

Error: 404 - https://api.github.com/repos/.../.../labels

When I copy & visit directly, it's found. What's the problems?

Would be nicer to look at than it currently is.

I don't know how I would run automated tests on this. :/

To allow it to do destructive things like remove tags that aren't in the config.

Also see #1

I suspect this is somehow related to my 2 factor auth, but every time I run the utility I just end up with a 404 error

org-labels add tas50 'feature request' d4c5f9
GitHub rate limit remaining: 4502
found 233 repositories in tas50

Error: 404 - https://api.github.com/repos/tas50/windows/labels

as in user/repo support

This may work better than the current implementation.

The idea is to take the tags from one repo and propagate them across the organization, updating existing tags and creating new ones accordingly.

I tried to add a label to the solid org, and it stopped with this error:

Error: 404 - https://api.github.com/repos/solid/solid-tpf/labels

I find that this repo doesn't have any labels, so that's probably the reason, but that shouldn't stop the script from adding some.