max-mapper / max-mapper/maintenance-modules
Validate pull requests with Travis
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 360
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I wrote a tool that can validate README links (valid URLs, not duplicate). It can be run when someone submits a pull request.
It is currently being used by
- https://github.com/vsouza/awesome-ios
- https://github.com/matteocrippa/awesome-swift
- https://github.com/dkhamsing/open-source-ios-apps
Examples
- https://travis-ci.org/matteocrippa/awesome-swift/builds/96526196 ok ✅
- https://travis-ci.org/matteocrippa/awesome-swift/builds/96722421 link redirected / rename 🔴
- https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/96763135 bad link / project deleted 🔴
- https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/95754715 dupe 🔴
If you are interested, connect this repo to https://travis-ci.org/ and add a .travis.yml file to the project.
See https://github.com/dkhamsing/awesome_bot for options, more information
Feel free to leave a comment 😄
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked awesome_bot options and the example .travis.yml, then connect this repository to Travis and add the project configuration. Done means pull requests automatically validate README URLs and detect duplicates, redirects, or missing projects as shown in the examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100