Skip to content

Commit 4a459df

Browse files
ayusharmajuanpicado
authored andcommitted
GitHub actions (conventional-changelog#32)
* chore: fixes snapshots test * chore: adds github actions, issue and feat templates * chore: fixes eslint * chore: remvoes circle ci and adds publish action * chore: adds github-release automation using actions
1 parent 96b65d9 commit 4a459df

File tree

12 files changed

+2139
-1972
lines changed

12 files changed

+2139
-1972
lines changed

.circleci/config.yml

-168
This file was deleted.

.github/ISSUE_TEMPLATE/Bug_report.md

+37
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
5+
---
6+
7+
**Describe the bug**
8+
A clear and concise description of what the bug is.
9+
10+
**To Reproduce**
11+
Steps to reproduce the behavior:
12+
1. Go to '...'
13+
2. Click on '....'
14+
3. Scroll down to '....'
15+
4. See error
16+
17+
**Expected behavior**
18+
A clear and concise description of what you expected to happen.
19+
20+
**Screenshots**
21+
If applicable, add screenshots to help explain your problem.
22+
23+
**Docker || Kubernetes (please complete the following information):**
24+
- Docker verdaccio tag: [e.g. verdaccio:beta]
25+
- Docker commands [e.g. docker pull ...]
26+
- Docker Version [e.g. v18.05.0-ce-rc1]
27+
28+
**Configuration File (cat ~/.config/verdaccio/config.yaml)**
29+
30+
**Debugging output**
31+
- `$ NODE_DEBUG=request verdaccio` display request calls (verdaccio <--> uplinks)
32+
- `$ DEBUG=express:* verdaccio` enable extreme verdaccio debug mode (verdaccio api)
33+
- `$ npm -ddd` prints:
34+
- `$ npm config get registry` prints:
35+
36+
**Additional context**
37+
Add any other context about the problem here.
+17
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
5+
---
6+
7+
**Is your feature request related to a problem? Please describe.**
8+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
9+
10+
**Describe the solution you'd like**
11+
A clear and concise description of what you want to happen.
12+
13+
**Describe alternatives you've considered**
14+
A clear and concise description of any alternative solutions or features you've considered.
15+
16+
**Additional context**
17+
Add any other context or screenshots about the feature request here.

.github/issue_template.md

+32
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
<!--
2+
First of all, please read this section
3+
4+
https://github.com/verdaccio/verdaccio/blob/master/CONTRIBUTING.md#reporting-a-bug
5+
6+
Some advices before file an issue
7+
* Give a brief explanation of the issue, suggestion or feature to request.
8+
* If the issue is a question, provide as much information you have available.
9+
* How can I do in order to reproduce it? What environment?
10+
* Define which version the issue happens and whether previous version the behavior is correct.
11+
* Provide your config file is really helpful. Please be aware to hide sensitive data (passwords, server IP, etc) before post.
12+
-->
13+
14+
#### My reason:
15+
#### Steps to reproduce:
16+
#### App Version:
17+
#### Config file:
18+
#### Additional information:
19+
20+
- `$ NODE_DEBUG=request verdaccio` display request calls (verdaccio <--> uplinks)
21+
- `$ DEBUG=express:* verdaccio` enable extreme verdaccio debug mode (verdaccio api)
22+
- `$ npm -ddd` prints:
23+
- `$ npm config get registry` prints:
24+
- Verdaccio terminal output
25+
- Which (Windows, OS X/macOS, or Linux) environment are you running verdaccio?:
26+
- Verdaccio configuration file, eg: `cat ~/.config/verdaccio/config.yaml`
27+
- Container Options:
28+
- Docker?:
29+
- Kubernetes?:
30+
31+
#### Additional verbose log:
32+

.github/main.workflow

+71
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
workflow "build and test" {
2+
resolves = [
3+
"lint",
4+
"test",
5+
"branch-filter",
6+
]
7+
on = "push"
8+
}
9+
10+
action "branch-filter" {
11+
uses = "actions/bin/filter@master"
12+
args = "branch"
13+
}
14+
15+
action "install" {
16+
uses = "docker://node:10"
17+
args = "yarn install"
18+
}
19+
20+
action "build" {
21+
uses = "docker://node:10"
22+
needs = ["install"]
23+
args = "yarn run build"
24+
}
25+
26+
action "lint" {
27+
uses = "docker://node:10"
28+
needs = ["install"]
29+
args = "yarn run lint"
30+
}
31+
32+
action "test" {
33+
uses = "docker://node:10"
34+
needs = ["build"]
35+
args = "yarn run test"
36+
}
37+
38+
workflow "release" {
39+
resolves = [
40+
"github-release",
41+
"tag-filter",
42+
"lint",
43+
]
44+
on = "push"
45+
}
46+
47+
action "tag-filter" {
48+
uses = "actions/bin/filter@master"
49+
args = "tag v*"
50+
}
51+
52+
action "publish" {
53+
needs = ["test"]
54+
uses = "docker://node:10"
55+
args = "sh scripts/publish.sh"
56+
secrets = [
57+
"REGISTRY_AUTH_TOKEN",
58+
]
59+
env = {
60+
REGISTRY_URL = "registry.verdaccio.org"
61+
}
62+
}
63+
64+
action "github-release" {
65+
needs = ["publish"]
66+
uses = "docker://node:10"
67+
args = "sh scripts/github-release.sh"
68+
secrets = [
69+
"GITHUB_TOKEN",
70+
]
71+
}

.github/pull_request_template.md

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
<!--
2+
3+
Before Pull Request check whether your commits follow this convention
4+
5+
https://github.com/verdaccio/verdaccio/blob/master/CONTRIBUTING.md#git-commit-guidelines
6+
7+
* If your PR fix an issue don't forget to update the unit test and documentation in /docs folder
8+
* If your PR delivers a new feature, please, provide examples and why such feature should be considered.
9+
* Document your changes /docs
10+
* Add unit test
11+
* Follow the commit guidelines in order to get a quick approval
12+
13+
Pick one/multiple type, if none apply please suggest one, we might be included it by default
14+
15+
eg: bug / feature / documentation / unit test / build
16+
17+
-->
18+
**Type:**
19+
20+
The following has been addressed in the PR:
21+
22+
* There is a related issue?
23+
* Unit or Functional tests are included in the PR
24+
25+
**Description:**
26+
27+
<!-- Resolves #??? -->

package.json

+4-2
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@verdaccio/ui-theme",
3-
"version": "0.0.4",
3+
"version": "0.0.12",
44
"description": "Verdaccio User Interface",
55
"author": {
66
"name": "Verdaccio Core Team"
@@ -15,6 +15,7 @@
1515
"@commitlint/config-conventional": "7.5.0",
1616
"@material-ui/core": "3.9.0",
1717
"@material-ui/icons": "3.0.2",
18+
"@octokit/rest": "16.23.2",
1819
"@verdaccio/babel-preset": "0.1.0",
1920
"@verdaccio/types": "5.0.0-beta.4",
2021
"autosuggest-highlight": "3.1.1",
@@ -43,6 +44,7 @@
4344
"flow-bin": "0.81.0",
4445
"flow-runtime": "0.17.0",
4546
"friendly-errors-webpack-plugin": "1.7.0",
47+
"get-stdin": "6.0.0",
4648
"github-markdown-css": "2.10.0",
4749
"html-webpack-plugin": "3.2.0",
4850
"husky": "0.15.0-rc.8",
@@ -107,7 +109,7 @@
107109
"flow": "flow check",
108110
"release": "standard-version -a -s",
109111
"test:clean": "npx jest --clearCache",
110-
"test": "cross-env NODE_ENV=test BABEL_ENV=test TZ=UTC FORCE_COLOR=1 jest --config ./jest.config.js --maxWorkers 2 --passWithNoTests",
112+
"test": "cross-env NODE_ENV=test BABEL_ENV=test TZ=UTC jest --config ./jest.config.js --maxWorkers 2 --passWithNoTests",
111113
"test:size": "bundlesize",
112114
"lint": "npm run flow && npm run lint:js && npm run lint:css",
113115
"lint:js": "eslint .",

0 commit comments

Comments
 (0)