Searched refs:team (Results 1 – 25 of 353) sorted by relevance
12345678910>>...15
30 const { team } = await mockTeam(t)32 team.exec([]),40 const { team, result } = await mockTeam(t)42 await team.exec(['add', '@npmcli:developers', 'foo'])48 const { team, result } = await mockTeam(t, {52 await team.exec(['add', '@npmcli:developers', 'foo'])61 const { team, result } = await mockTeam(t, {65 await team.exec(['add', '@npmcli:developers', 'foo'])71 team: 'npmcli:developers', property79 const { team, result } = await mockTeam(t, {[all …]
85 registry.setPermissions({ spec: '@npmcli/test-package', team: '@npm:test-team', permissions }) property104 registry.removePermissions({ spec: '@npmcli/test-package', team: '@npm:test-team' }) property130 registry.getPackages({ team: '@npm:test-team', packages }) property146 registry.getPackages({ team: 'npm', packages }) property160 registry.getPackages({ team: '@npm:test-team', packages }) property
8 exports[`test/lib/commands/team.js TAP team add <scope:team> <user> --parseable > should output suc…12 exports[`test/lib/commands/team.js TAP team add <scope:team> <user> default output > should output …16 …orts[`test/lib/commands/team.js TAP team create <scope:team> --parseable > should output parseable…20 exports[`test/lib/commands/team.js TAP team create <scope:team> default output > should output succ…24 exports[`test/lib/commands/team.js TAP team destroy <scope:team> --parseable > should output parsea…28 …xports[`test/lib/commands/team.js TAP team destroy <scope:team> default output > should output suc…32 exports[`test/lib/commands/team.js TAP team ls <scope:team> --parseable > should list users for a p…39 exports[`test/lib/commands/team.js TAP team ls <scope:team> default output > should list users for …47 exports[`test/lib/commands/team.js TAP team ls <scope:team> no users > should list no users for a g…51 exports[`test/lib/commands/team.js TAP team ls <scope:team> single user > should list single user f…[all …]
9 team` command and its various subcommands.14 const team = require('libnpmteam')17 console.log(await team.lsTeams('npm'))41 * [team opts](#opts)70 #### <a name="create"></a> `> team.create(team, [opts]) -> Promise`72 Creates a team named `team`. Team names use the format `@<scope>:<name>`, with80 await team.create('@npm:cli', {token: 'myregistrytoken'})81 // The @npm:cli team now exists.84 #### <a name="destroy"></a> `> team.destroy(team, [opts]) -> Promise`86 Destroys a team named `team`. Team names use the format `@<scope>:<name>`, with[all …]
2 title: npm-team4 description: Manage organization teams and team memberships10 npm team create <scope:team> [--otp <otpcode>]11 npm team destroy <scope:team> [--otp <otpcode>]12 npm team add <scope:team> <user> [--otp <otpcode>]13 npm team rm <scope:team> <user> [--otp <otpcode>]14 npm team ls <scope>|<scope:team>21 Used to manage teams in organizations, and change team memberships. Does not26 `newteam` team in an `org` organization, you must always refer to that team35 Create a new team, or destroy an existing one. Note: You cannot remove the[all …]
10 npm access list packages [<user>|<scope>|<scope:team> [<package>]15 npm access grant <read-only|read-write> <scope:team> [<package>]16 npm access revoke <scope:team> [<package>]41 Show all of the packages a user or a team is able to access, along with the66 * You are a member of the team that owns a scope.68 of a team or directly as an owner.77 Management of teams and team memberships is done with the `npm team` command.120 * [npm team](/commands/npm-team)
12 2. Team admin, manages team membership & package access.15 …n will use the website to manage membership. Every org has a `developers` team that all users are …17 The team admin is the person who manages team creation, team membership, and package access for tea…23 1. `npm team` see [npm team](/commands/npm-team) for more details31 npm team ls <org>:developers34 … is automatically given a `developers` team, so you can see the whole list of team members in your…36 * Create a new team:39 npm team create <org:team>42 * Add members to that team:45 npm team add <org:team> <user>[all …]
11 const { scope, team } = splitEntity(entity)12 validate('SSO', [scope, team, opts])18 body: { name: team, description: opts.description },24 const { scope, team } = splitEntity(entity)25 validate('SSO', [scope, team, opts])26 const uri = `/-/team/${eu(scope)}/${eu(team)}`37 const { scope, team } = splitEntity(entity)38 validate('SSO', [scope, team, opts])39 const uri = `/-/team/${eu(scope)}/${eu(team)}/user`49 const { scope, team } = splitEntity(entity)[all …]
19 const [scope, team] = scopeTeam.slice(slice).split(':').map(encodeURIComponent) constant20 return { scope, team }24 const { scope, team } = parseTeam(scopeTeam)27 if (team) {28 uri = `/-/team/${scope}/${team}/package`101 const { scope, team } = parseTeam(scopeTeam)102 if (!scope || !team) {105 const uri = `/-/team/${scope}/${team}/package`119 const { scope, team } = parseTeam(scopeTeam)120 const uri = `/-/team/${scope}/${team}/package`
43 #### `access.getPackages(user|scope|team, opts) -> Promise<Object>`45 Gets all packages for a given user, scope, or team.47 Teams should be in the format `scope:team` or `@scope:team`55 #### `access.removePermissions(team, spec, opts) -> Promise<Boolean>`57 Removes the access for a given team to a package.59 Teams should be in the format `scope:team` or `@scope:team`84 #### access.setPermissions(team, spec, permssions, opts) -> Promise<Boolean>`86 Sets permissions levels for a given team to a package.88 Teams should be in the format `scope:team` or `@scope:team`
7 * Add them to the security-stewards team in the GitHub nodejs-private9 * Add them to the [public website team](https://github.com/orgs/nodejs/teams/website).11 * Add them to the standard team in H1 using this18 * Remove them from security-stewards team in the GitHub nodejs-private20 * Remove them from public website team22 standard team in H1 using this
20 * The next-10 team reaches out to teams/groups on an ad hoc basis22 * The next-10 team reaches out to those who publish newsletters ad hoc33 * [security-team](https://github.com/nodejs/security-wg/issues/1006).
210 pub team: team_id,220 pub team: team_id,235 pub team: team_id,249 pub team: team_id,262 pub team: team_id,866 team: team_id, in _get_next_area_info()907 pub fn set_port_owner(port: port_id, team: team_id) -> status_t; in set_port_owner()939 pub fn set_sem_owner(id: sem_id, team: team_id) -> status_t; in set_sem_owner()942 team: team_id, in _get_next_sem_info()948 pub fn kill_team(team: team_id) -> status_t; in kill_team()[all …]
15 issue to only the reporter and the project's security team.38 - A person in the security team sends an e-mail to the original reporter to41 - The security team investigates the report and either rejects it or accepts44 - If the report is rejected, the team writes to the reporter to explain why.46 - If the report is accepted, the team writes to the reporter to let him/her49 - The security team discusses the problem, works out a fix, considers the71 - The security team commits the fix in a private branch. The commit message80 - The project team creates a release that includes the fix.82 - The project team announces the release and the vulnerability to the world in
73 team: entity, property87 team: entity, property101 team: entity, property116 team: entity, property
3 ("meeting", "with team."),8 "Flow tasks": [ ("meeting", "with team"), ("meeting", "with boss") ],
3 - meeting: with team.7 Flow tasks: !!pairs [ meeting: with team, meeting: with boss ]
3 As part of the Chromium team, the V8 team is committed to preserving and
58 The curl security team is the sole arbiter if a reported flaw is subject to a64 performed by the curl security team. The grading will be based on the CVSS69 The curl security team gives the vulnerability a score or severity level, as77 or its security team never actually receive any of this money, hold the money,
93 make sure that we always have the list of maintainers as "the team that push99 ## Security team members101 We have a security team. That is the team of people who are subscribed to the106 The security team works best when it consists of a small set of active107 persons. We invite new members when the team seems to need it, and we also108 expect to retire security team members as they "drift off" from the project or
34 - A person in the security team responds to the original report to acknowledge37 - The security team investigates the report and either rejects it or accepts41 - If the report is rejected, the team writes to the reporter to explain why.43 - If the report is accepted, the team writes to the reporter to let them46 - The security team discusses the problem, works out a fix, considers the67 - The security team commits the fix in a private branch. The commit message74 Bounty team and the reporter is asked to request the reward from them after90 - The project team creates a release that includes the fix.92 - The project team announces the release and the vulnerability to the world in145 The curl project's security team rates security problems using four severity
24 ## ICU team member pages26 Other documentation pages here are written by and for team members.
12 Copyright (c) 2000-2017 Expat development team13 Copyright (c) 2017 Expat development team16 Copyright (c) 2019 Expat development team
31 set, shrinkwrap, star, stars, start, stop, team, test,81 start, stop, team, test,133 start, stop, team, test,172 set, shrinkwrap, star, stars, start, stop, team, test,222 start, stop, team, test,274 start, stop, team, test,325 start, stop, team, test,364 set, shrinkwrap, star, stars, start, stop, team, test,401 set, shrinkwrap, star, stars, start, stop, team, test,438 set, shrinkwrap, star, stars, start, stop, team, test,
8 **Note**: These mailing lists are not maintained by the libsndfile team anymore.9 Use [GitHub issues and pull requests instead](https://docs.github.com/en/free-pro-team@latest/githu…