Migration to travis-ci.com

Open
#119 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
ci-cd

Research direction

Review the Travis CI migration guide linked in the issue and locate this repository's Travis CI configuration and current build entry points. Update the configuration for travis-ci.com and the GitHub App migration, then verify that automated testing runs successfully there.

Written by the indexing model from the issue text.

Description

Accessing a travis-build-report shows at the top:
"Since June 15th, 2021, the building on travis-ci.org is ceased. Please use travis-ci.com from now on."

Please follow the migration guide to re-enable automated testing for the mailvelope-projects:
https://docs.travis-ci.com/user/migrate/open-source-repository-migration/#migrating-a-repository

According to the communication of travis, they want to merge the opensource and private projects on one domain while changing their github-access approach from oauth to github-app. No financial consequences for open source projects.

Dominant language
JavaScript
Stars
481
Forks
80
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mailvelope/keyserver

All issues in mailvelope/keyserver

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.