Comments (4)
@bduffey-pe Thanks for raising the issue and pull request π
I'm not quite sure what you mean by "local" yet. By looking at the logic in your PR #77, perhaps, you'd like to use the configuration file that in the target branch, not in the source branch?
I can't remember what context.ref
returns exactly but I think it returns:
The fully-formed ref of the branch or tag that triggered the workflow run
ref: https://docs.github.com/en/actions/learn-github-actions/contexts
So if you use pull_request
, it should return the target branch whereas pull_request_event
returns the source branch. I'm not 100% sure though.
Which event do you use?
from auto-request-review.
Hey @necojackarc , thanks for the reply! I agree that my usage of local is ambiguous. In this case, local means local to this script executing (as in within the container that is running when this script executes in GitHub Actions). For our team specifically, we have one reviewer yaml file that has many developers (10+) and many groups (currently 9), and storing this individually in each of our many repos (15+) would be a nightmare to maintain.
So, we store this file elsewhere (for us that's Azure Storage but it could just as easily be S3 or Google Drive or any place where a file can be downloaded from) and just wget it immediately prior to running this script. So the file is never in our repo at all and I don't want this script to look for it there.
For others, whether they choose to keep the file externally or not, if they shallow clone their PR branch before the script runs, it will pick up the latest version of this file, which means it will work for brand new PRs as well where the file is in the PR and not in the repo yet. That was my reference to it solving #12 .
Since I made it a config that by default is false (behavior today) it seemed like a nice way to work for both my (and hopefully others' needs) as well as continue to work for you and anyone relying on its functionality today. Does that help explain it better?
from auto-request-review.
we store this file elsewhere (for us that's Azure Storage but it could just as easily be S3 or Google Drive or any place where a file can be downloaded from) and just wget it immediately prior to running this script. So the file is never in our repo at all and I don't want this script to look for it there.
This is quite an interesting use case!
Ideally speaking, perhaps, you may want to add the direct URL to the stored file such as in S3 with the necessary credentials so that the Action can directly download the config, but I feel this is a good middle ground as it's simple enough.
I'll give some feedback on your pull request π
from auto-request-review.
#77 has resolved this issue. I'm going to make a new release π
from auto-request-review.
Related Issues (20)
- Remove reviewer when PR is converted to draft
- Don't set auto reviewers if theyβre already set manually
- What is the permission required?
- Unable to use github team HOT 4
- "explode" GitHub team when using as a reviewer group
- Github Team doesn't work as a group
- Don't re-request review if approval is already present for that reviewer HOT 1
- "last_files_match_only" does not work when pattern owner is a team HOT 1
- bug: workflow failed due to trying to request author as reviewer HOT 1
- "last_files_match_only=true" only adds one alias as a reviewer, regardless of number of edited files
- Github - Node.js 16 actions are deprecated. HOT 1
- Migrate from CODEOWNERS to this format
- Bump to Node.js 16 HOT 1
- Multiple glob patterns for the same group of reviewers HOT 2
- Error: Parameter token or opts.auth is required in PR opened by dependabot HOT 1
- bug: workflow fails on forks HOT 1
- Support for monorepo / cross-team repositories HOT 4
- Trying to parse config throwing vague error HOT 1
- Mention non-collaborators instead of requesting review from them and fail HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from auto-request-review.