Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add build badge & remove reference to circleCI #660

Merged
merged 3 commits into from
May 3, 2024
Merged

add build badge & remove reference to circleCI #660

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5d7cf60
add build badge & remove reference to circleCI
JeffGreiner-eaton Apr 30, 2024
2c50a82
use yarn --immutable
JeffGreiner-eaton May 1, 2024
6217de9
update immutable
JeffGreiner-eaton May 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 14 additions & 14 deletions .github/workflows/blui-ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
name: CI Run
name: Build

on:
push:
Expand Down Expand Up @@ -76,7 +76,7 @@ jobs:
with:
node-version: ${{ matrix.node-version }}
cache: 'yarn'
- run: yarn --frozen-lockfile
- run: yarn --immutable
- run: yarn build:lib
- name: Save build
uses: actions/upload-artifact@v3
Expand Down Expand Up @@ -135,7 +135,7 @@ jobs:
node-version: ${{ matrix.node-version }}
cache: 'yarn'
- run: yarn initialize
- run: yarn --frozen-lockfile
- run: yarn --immutable
working-directory: showcase
- name: Download tarball
uses: actions/download-artifact@v3
Expand Down Expand Up @@ -183,14 +183,14 @@ jobs:
with:
node-version: ${{ matrix.node-version }}
cache: 'yarn'
- run: yarn --frozen-lockfile
- run: yarn build:lib
- run: yarn --immutable
surajeaton marked this conversation as resolved.
Show resolved Hide resolved
- run: yarn build:demo
- name: Save build
uses: actions/upload-artifact@v3
with:
name: dist
name: build
if-no-files-found: error
path: dist
path: build

deploy_angular_doc_site_dev:
runs-on: ubuntu-latest
Expand All @@ -204,12 +204,12 @@ jobs:
- name: Download build
uses: actions/download-artifact@v3
with:
name: dist
path: dist
name: build
path: build
- name: deploy
uses: JamesIves/github-pages-deploy-action@v4
with:
folder: dist
folder: build
token: ${{env.DEV_DEPLOY_TOKEN}}
repository-name: brightlayer-ui-components/angular-dev
branch: master
Expand All @@ -229,12 +229,12 @@ jobs:
- name: Download build
uses: actions/download-artifact@v3
with:
name: dist
path: dist
name: build
path: build
- name: deploy
uses: JamesIves/github-pages-deploy-action@v4
with:
folder: dist
folder: build
token: ${{env.DEV_DEPLOY_TOKEN}}
repository-name: brightlayer-ui-components/angular
branch: master
Expand Down Expand Up @@ -263,5 +263,5 @@ jobs:
with:
node-version: ${{ matrix.node-version }}
registry-url: 'https://registry.npmjs.org'
- run: yarn --frozen-lockfile
- run: yarn --immutable
- run: npm run publish:package -b ${{env.BRANCH}}
4 changes: 2 additions & 2 deletions PUBLISHING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Automatic Publishing

This package is published to NPM automatically by CircleCI when code is merged into the `dev` or `master` branches. To publish a new version, simply update the version in `package.json` and merge your code into the appropriate branch.
This package is published to NPM automatically by Github when code is merged into the `dev` or `master` branches. To publish a new version, simply update the version in `package.json` and merge your code into the appropriate branch.

- The `dev` branch will publish versions marked as `alpha` or `beta`.
- The `master` branch will publish any version (`alpha`, `beta`, or `latest`).
Expand All @@ -26,4 +26,4 @@ yarn build:lib
npm adduser && yarn publish:package
```

> Publishing manually should only be done for `alpha` or `beta` packages. The command will work for `latest` packages, but this should be avoided except in rare situations where the automatic publishing functionality is not working in CircleCI.
> Publishing manually should only be done for `alpha` or `beta` packages. The command will work for `latest` packages, but this should be avoided except in rare situations where the automatic publishing functionality is not working in Github.
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Brightlayer UI Angular Components

[![](https://img.shields.io/circleci/project/github/etn-ccis/blui-angular-component-library/master.svg?style=flat)](https://circleci.com/gh/etn-ccis/blui-angular-component-library/tree/master)
[![Build](https://github.com/etn-ccis/blui-angular-component-library/actions/workflows/blui-ci.yml/badge.svg?branch=master)](https://github.com/etn-ccis/blui-angular-component-library/actions/workflows/blui-ci.yml)
![npm](https://img.shields.io/npm/v/@brightlayer-ui/angular-components?label=%40brightlayer-ui%2Fangular-components) [![codecov](https://codecov.io/gh/etn-ccis/blui-angular-component-library/branch/master/graph/badge.svg?token=DB9EMVFAFJ)](https://codecov.io/gh/etn-ccis/blui-angular-component-library)

This is a library of custom components for use in Brightlayer UI applications. For the most part, these components are meant to simplify building your application by providing re-usable components that implement common use cases in Brightlayer UI and eliminating the need to multiple teams to build their own components for these.
Expand Down
Loading