GGLinnk
/
foris-js
mirror of https://gitlab.nic.cz/turris/reforis/foris-js.git
1
0
Fork 0
Code Issues Releases Activity
Foris JS library is a set of components and utils for reForis and plugins.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
102 Commits
7 Branches
49 Tags
8.2 MiB
 
 
 
 
Tag: Branch: Tree: 73f4ab48c3
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '73f4ab48c3'
${ noResults }
Maciej Lenartowicz 73f4ab48c3
Added virtual environment and packages required for translations. 		5 years ago
docs Core review docs fixes. 5 years ago
scripts Fixed publish script 5 years ago
src Improve error handling + small refactoring. 5 years ago
translations Added virtual environment and packages required for translations. 5 years ago
.eslintignore Extract the library from reforis. 5 years ago
.eslintrc.js Shared lint configs 5 years ago
.gitignore Added virtual environment and packages required for translations. 5 years ago
.gitlab-ci.yml Flat structure of published package 5 years ago
Makefile Added virtual environment and packages required for translations. 5 years ago
README.md Changed beta versioning procedure 5 years ago
babel.cfg Add translations. 5 years ago
babel.config.js Flat structure of published package 5 years ago
jest.config.js Move css to the library. 5 years ago
package-lock.json Shared lint configs 5 years ago
package.json Shared lint configs 5 years ago
requirements.txt Added virtual environment and packages required for translations. 5 years ago
styleguide.config.js Download docs css via NPM. 5 years ago

README.md

foris-js

Publishing package

Beta versions

Each commit to dev branch will result in publishing a new version of library tagged beta. Versions names are based on commit SHA, e.g. foris@0.1.0-beta.d9073aa4.

Preparing a release

  1. Crete a merge request to dev branch with version bumped
  2. When merging add [skip ci] to commit message to prevent publishing unnecessary version
  3. Create a merge request from dev to master branch
  4. New version should be published automatically