-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Team project builds are failing because now inspect
uses default scope
#50
Comments
Hi, @Regaddi {
"github": {
"enabled": false
},
"version" : 2,
"scope": "my-team"
} I will add this feature to the next version. |
Hey @amondnet, thanks for your response! This is the configuration file: {
"version": 2,
"scope": "my-team",
"builds": [
{
"src": "/packages/dashboard/package.json",
"use": "@now/next"
}
],
"routes": [
{
"src": "/(.*)",
"dest": "/packages/dashboard/$1",
"continue": true
}
]
}
Thanks! |
hi @Regaddi , - uses: vercel-action@v19 //v19.0.1+1
id: vercel-action
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
vercel-token: ${{ secrets.VERCEL_TOKEN }}
vercel-org-id: ${{ secrets.VERCEL_ORG_ID_TEAM_SCOPE }}
vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID_TEAM_SCOPE }}
working-directory: example/team-scope
scope: ${{ secrets.VERCEL_SCOPE }} |
It's working perfectly! Thanks! |
Hey 👋
It would be good to be able to configure the
--scope
flag fornow inspect
.By default it uses my personal space, but when deploying a team project it should instead search within the team scope.
Example output:
This leads to failing builds, because the team project can't be found within my personal scope.
It used to work with now 18.0.0, but fails with now 19.0.1.
Thanks in advance for your help!
The text was updated successfully, but these errors were encountered: