Feature Request: PAT Management

[rkrug]

When backing up different organisations, different PATs might be needed. It would be useful to be able to supply the PAT as an argument to the function with a default value of NULL leading to the current behaviour.

I have though no idea how much re-writing would be necessary for this...

[mpadge]

@rkrug General approach for that these days is to call function via withr:

withr::with_envvar(
  list("GITHUB_PAT" = <token>),
  myfn()
)

Hard-coding tokens as function arguments can be unsafe, and is rightly frowned upon these days, so I'd suggest that as your best approach, but we should also wait to see what @maelle has to say.

[maelle]

I agree with @mpadge. If needed we can add the example to the docs?

[rkrug]

If this is the general approach, I am fine with it. But I am not hard-coding the PAT, but providing a function call to retrieve it. I agree - hard coding the PAT is bad.

@maelle An example would be nice. Thanks. And also the explicit mentioning that flow in which the PAT is determined (keychain? Environmental variable?) would be useful to deal with the need for different PATs.

Please feel free to close - I just leave it open as @maelle suggested an example.

[maelle]

@rkrug would you be willing to make a PR? 😸