raulcd commented on issue #47075: URL: https://github.com/apache/arrow/issues/47075#issuecomment-3072340045
> [@raulcd](https://github.com/raulcd): I could get behind the one-token idea I think. I like the `ARROW_`/`CROSSBOW_` prefixed tokens since I set them as shell-global and don't worry about them. If we used just GH_TOKEN, would you set them shell-global, would you use a dotenv style approach, or something else? The only one I use regularly is the one required for the merge script. I have a config file defined at `~/.config/arrow/merge.conf`, which is the config file the merge script reads to retrieve the token. https://github.com/apache/arrow/blob/main/dev/merge_arrow_pr.py#L571 and https://github.com/apache/arrow/blob/main/dev/merge.conf.sample For release/crossbow tasks, I have a small snippet stored which I copy paste with all the export `ARROW_GITHUB_TOKEN`, `CROSSBOW_GITHUB_TOKEN` but I don't use those often so it doesn't bother me to have to do it that way. I would say that in general committers (unless doing release tasks or wanting to manually push crossbow jobs) don't require to define those if they use the `merge.conf` file. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
