GithubHelp home page GithubHelp logo

Comments (8)

russmatney avatar russmatney commented on June 30, 2024 1

Indeed, it was helpful immediately to unblock my local testing!

I added some thoughts on caching requests as a potential solution for local dev/testing (and faster neil performance) here: #127 (comment) i can port this over to a new discussion/issue if there's interest, feel free to ping me!

from neil.

teodorlu avatar teodorlu commented on June 30, 2024

The rate limit seems to be a common pitfall for new contributors to this project so we may want to add something to the README as well. Maybe some better error handling for the rate-limiting HTTP response too.

Is it possible to check whether we've hit the rate limit directly in the tests, and stop with a good error message?

from neil.

borkdude avatar borkdude commented on June 30, 2024

This is how I use GITHUB_TOKEN in gh-release-artifact: https://github.com/borkdude/gh-release-artifact/blob/cf082df46a648178d1904e9cbcb787d8136a35c6/src/borkdude/gh_release_artifact.clj#L19, if anyone wants to put together a PR.

from neil.

rads avatar rads commented on June 30, 2024

@borkdude: It seems like it could lead to confusion if we just start using whatever GITHUB_TOKEN is defined without documenting that as part of the public neil behavior. I expect using a GitHub token would be gated by a --dev mode or simple prefixing like I did in my example (BABASHKA_NEIL_DEV_GITHUB_TOKEN).

Otherwise if we do want people to be able to use their own GITHUB_TOKEN for non-dev neil usage, we can document that. I just want to make sure we aren't doing this implicitly.

What do you think?

from neil.

borkdude avatar borkdude commented on June 30, 2024

Sounds good!

from neil.

teodorlu avatar teodorlu commented on June 30, 2024

We merged @rads' proposed solution in #110. BABASHKA_NEIL_DEV_GITHUB_TOKEN is now used if set.

Though I don't think this behavior is documented anywhere.

Cc @russmatney

from neil.

rads avatar rads commented on June 30, 2024

Thanks for taking care of this! Since this issue is specific to the dev experience, this is now resolved from my point of view.

If we want to expand the scope here to improve the experience for end users too, let’s create a new issue for that.

from neil.

teodorlu avatar teodorlu commented on June 30, 2024

Sounds good πŸ‘

I'm happy with the current solution as-is.

I suspect that for end users, many won't appreciate extra mandatory setup.

from neil.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.