Skip to content

Request to enable Travis CI for nodejs/i18n repo #149

@zeke

Description

@zeke

We want to enable Travis CI on the nodejs/i18n repo.

Based on discussions with @joyeecheung, @Trott, and @mcollina, the recommended process is the following:

  1. move the nodejs/i18n repo temporarily to my personal @zeke account
  2. enable Travis CI
  3. move the repo back to @nodejs
  4. Land chore: enable Travis CI for i18n repo github-bot#171 in order to whitelist the i18n repo

I already have admin privileges on the i18n repo, so I am unblocked for 1,2,3. Step 4 will require help from someone else who has permission to merge PRs on the github-bot repo.

Is all this okay?

Related:

cc @obensource

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions