Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/npm/cli.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/.github
AgeCommit message (Collapse)Author
2021-02-13docs: remove npm v6 issue templateDarcy Clarke
2021-02-13docs: update github issue linksDarcy Clarke
2021-02-12[fix] node v10.0 lacks `fs.promises`Jordan Harband
In this node version, fall back to `util.promisify` of the callback version. Maybe fixes https://github.com/npm/cli/issues/2623. Maybe fixes https://github.com/npm/cli/issues/2652. Maybe fixes https://github.com/npm/cli/issues/2625. PR-URL: https://github.com/npm/cli/pull/2654 Credit: @ljharb Close: #2654 Reviewed-by: @wraithgar, @ruyadorno
2021-02-12[tests] separate tests from linting and license validationJordan Harband
PR-URL: https://github.com/npm/cli/pull/2682 Credit: @ljharb Close: #2682 Reviewed-by: @wraithgar
2020-12-18update ISSUE_TEMPLATE with modern linksisaacs
2020-11-16Update config.ymlDarcy Clarke
2020-10-30chore: cleanup makefilenlf
- fix prune target - fix ci build - run rebuild after install PR-URL: https://github.com/npm/cli/pull/2068 Credit: @nlf Close: #2068 Reviewed-by: @ruyadorno
2020-10-13chore: add issue templates back & remove legacy settings.ymlDarcy Clarke
2020-09-22Add a 'check-coverage' script so we can track towards completionisaacs
We are targetting 100% test coverage for npm v7 GA. Using a coverage-map, we require that any of the newly created tests fully cover the module that they are testing. However, this has the side effect of _always_ hitting 100% coverage when running 'npm test', even though not all modules are being tested. This adds a new 'load-all' test which, in 'check-coverage' mode, tells nyc to include every file in the project. This also removes the double-run of our tests in CI, where we run once and then immediately run the same exact thing again for Coveralls, and sends the 'check-coverage' output to Coveralls instead. PR-URL: https://github.com/npm/cli/pull/1820 Credit: @isaacs Close: #1820 Reviewed-by: @ruyadorno
2020-08-04Actions: remove v6 and v8, add v14isaacs
Accidentally landed this in the v7 branch, didn't realize it was based on v6.
2020-08-04GitHub Actions: add a win32 bash workflowEdward Thomson
Update the matrix to have two Windows workflows: one running PowerShell and one running bash.
2020-07-29update CI test script for travisisaacs
2020-07-23Temporarily only run unit tests while beta work in progressisaacs
2020-05-08feat: drop support for node v6 and v8claudiahdz
2020-05-01chore: reenable windows ciRuy Adorno
2020-01-28feat: updated workflow for pull-ruquest benchmark dispatch requestsMichael Perrotte
2020-01-28feat: added workflow file for commenting on a pull-request to dispatch ↵Michael Perrotte
trigger benchmark suite
2020-01-28fix: removed authorization header from benchmark dispatch requestMichael Perrotte
2020-01-23Use the npm lint script on CI.XhmikosR
This should be more consistent since it should use the specified standard version and not the latest one. PR-URL: https://github.com/npm/cli/pull/604 Credit: @XhmikosR Close: #604 Reviewed-by: @mikemimik
2020-01-09chore: ci cleanupRuy Adorno
- Moved windows builds to travis-only since they're currently failing on GHA and it's not code-related - Added setup on GHA config to only run coverage once in ubuntu target
2020-01-07CI: switch to `actions/checkout@v2`XhmikosR
PR-URL: https://github.com/npm/cli/pull/600 Credit: @XhmikosR Close: #600 Reviewed-by: @ruyadorno
2020-01-07CI: add `fail-fast: false`XhmikosR
This will allow all builds to run even if one fails PR-URL: https://github.com/npm/cli/pull/601 Credit: @XhmikosR Close: #601 Reviewed-by: @ruyadorno
2019-11-14feat: added workflow to trigger and run benchmarks [2]Michael Perrotte
PR-URL: https://github.com/npm/cli/pull/278 Credit: @mikemimik Close: #278 Reviewed-by: @claudiahdz
2019-11-05chore: create settings.yml fileDarcy Clarke
- This will ensure we inherit our standard labels from the `open-source-project-boilerplate` PR-URL: https://github.com/npm/cli/pull/282 Credit: @darcyclarke Close: #282 Reviewed-by: @ruyadorno
2019-10-31use github actions for CIJason Etcovitch
PR-URL: https://github.com/npm/cli/pull/272 Credit: @JasonEtco Close: #272 Reviewed-by: @ruyadorno
2018-07-18docs: replace troubleshooting.md with posts (#17)Daijiro Wachi
Refs: https://github.com/npm/cli/pull/5 PR-URL: https://github.com/npm/cli/pull/17/ Credit: @watilde Reviewed-By: @zkat
2018-03-09docs: Add a common open reason to the issue template (#19893)Kyle Spier-Swenson
`npm is doing something I don't understand.` is often inappropriately used when the author means `npm is producing incorrect or undesirable behavior.`. I only had to look thru the first page of open issues to find 5 examples of this. PR-URL: https://github.com/npm/npm/pull/19893 Credit: @MrStonedOne Reviewed-By: @zkat
2017-07-09github: cli-team instead of employeesRebecca Turner
2017-07-09github: Experiment with adding PR ownersRebecca Turner
2017-03-10docs: update troubleshooting and contribution guide links (#15960)Daijirō Wachi
PR-URL: https://github.com/npm/npm/pull/15960 Credit: @watilde Reviewed-By: @zkat
2016-10-07issue_template: OSX is now called macOS, update to reflect thisAlex Chesters
Credit: @AlexChesters Reviewed-By: @iarna PR-URL: https://github.com/npm/npm/pull/14010
2016-06-30doc: tweak issue templateForrest L Norvell
- move important bits to top - condense supporting info down to a smaller section - more structured request for proxy & network info
2016-06-25doc: tweak formatting for issue templateForrest L Norvell
2016-06-25doc: tweak issue templateForrest L Norvell
- moved to .github to keep top-level directory clean - expanded feature request section - tweaked formatting
    generated by cgit v1.2.3 (git 2.25.1) at 2024-08-25 00:29:59 +0300