refactor: move handlers and new nesting on the example of 2 endpoints from ItemsControlller to Application folder#37
Open
SaraevaAnastasia wants to merge 29 commits intofeature/proposal-for-api-reorganizationfrom
Conversation
SaraevaAnastasia
changed the base branch from
master
to
feature/proposal-for-api-reorganization
…sion using Conventional Commits in __version file, trigger deploy on automatic release commits only (#41) * feat: add semantic-release * feat: change .releaserc.json config * ci: add semantic-release workflow to automatically create and update tags * fix: change successCmd to verifyReleaseCmd to rewrite version in __version file * chore(release): 1.0.1 * infra: return the version to 1.0.0 * chore(release): 1.0.1 * refactor: remove redundant token in checkout step * chore(release): 1.0.2 * chore: return color theme settings * feat: created a separate file for the release rules also change verifyReleaseCmd to prepareCmd * chore(release): 1.1.0 * ci: rename workflow to release-new-version-from-default.yml * ci: rename files to release.config.cjs and release.rules.cjs to stay together in files explorer and better match the docs that expects module.exports sytax for release.config file not for .releaserc where it should be YAML or JSON * ci: remove extra blank line from __version, it might be a small problem for future automation, it is better to be a single line with the version and nothing more * ci: minor improvements of release-new-version-from-default.yml to make it alike others in the repo, upgrade version of the used actions to latest inclding Node.js * ci: try to get rid of angular preset in favor of conventional commits illuminating an issue with ! to mark breaking changes, explicitly add release false for no deployment types according to the issue * ci: install missing conventional-changelog-conventionalcommits preset * refactor!: fix versions and try to trigger a major release * chore(release): 1.1.1 * fix!: improve comment and try to make a breaking change fix * chore(release): 2.0.0 * cd: remove not needed comment, text cd patch release * chore(release): 2.0.1 * feat: try a feature release * chore(release): 2.1.0 * fix: try to remove possibly not needed permission * chore(release): 2.1.1 * fix: try to remove another possibly not needed permission * git: ignore semantic-release related config files in .dockerignore * chore(release): 2.1.2 * Revert "fix: try to remove another possibly not needed permission" This reverts commit 34c6df2. * feat!: target master branch * Revert "feat!: target master branch" This reverts commit f837950. * ci: comment failing pipeline to test deployment and releases from fb before master * feat!: try to trigger deploy to prod by a new release publishing * chore(release): 3.0.0 * ci: temp remove workflow * fix: trigger deploy * chore(release): 3.0.1 * fix: trigger deploy by new tag * chore(release): 3.0.2 * fix: trigger deploy by new tag * * chore(release): 3.0.3 * fix: try to fix deploy trigger on release commit only * chore(release): 3.0.4 [deploy to prod] * ci: fix deploy-to-prod-from-default.yml ignoring docker build for non [deploy to prod] commits * ci: fix step name in .reusable-e2e-tests-against-prod.yml * cleanup: prepare for merge * cleanup: initial version is 1.0.0 --------- Co-authored-by: semantic-release-bot <semantic-release-bot@martynus.net> Co-authored-by: Aleksandr Shinkarev <ashinkarev@tourmalinecore.com>
… failing due to some weird error, later will be returned as figured out and addressed, try to fix deployment trigger (#42) * ci: remove semantic-release github plugin to fix the workflow that is failing due to some weird error, later will be returned as figured our and addressed * ci: try to fix deployment trigger --------- Co-authored-by: Aleksandr Shinkarev <ashinkarev@tourmalinecore.com>
…if it was a temporal issue, trigger deploy (#43) Co-authored-by: Aleksandr Shinkarev <ashinkarev@tourmalinecore.com>
… after a release commit because otherwise the release commit triggers no workflows as the default GitHub policy to avoid infinite loops of workflows (#44) * ci: change branch name from master to this fb * chore(release): 1.0.1-a [deploy to prod] * fix: use personal token so that another workflow can be triggered by a semantic-release commit * ci: change branch name from master to this fb * chore(release): 1.0.2 [deploy to prod] * fix: try to use persist-credentials false to commit using a needed token * chore(release): 1.0.3 [deploy to prod] * ci: cleanup and add needed comments to the final release and deploy workflows --------- Co-authored-by: Aleksandr Shinkarev <ashinkarev@tourmalinecore.com> Co-authored-by: semantic-release-bot <semantic-release-bot@martynus.net>
…ts extra run that is not harming but not needed (#45) * ci: add paths-ignore to not trigger release-new-version-from-default.yml on its resulting commit * chore(release): 1.0.2-a [deploy to prod] * ci: cleanup branches name --------- Co-authored-by: Aleksandr Shinkarev <ashinkarev@tourmalinecore.com>
…naming convention avoiding snake case naming (#36)
…version file (#47) * ci: try to tag built docker images with __version file content adding testing temp-docker-build-tagged-with-version.yml * cleanup: remove testing temp-docker-build-tagged-with-version.yml --------- Co-authored-by: Aleksandr Shinkarev <ashinkarev@tourmalinecore.com>
…time-api version of the related steps (#48) * ci: use fixed steps from time-api * ci: test parallel readme changes modifying it * docs(readme): bring test coverage score up to date * ci: trigger parallel commit * docs(readme): Update Mermaid DB Schema Diagram in README.md (siren-gen) * ci: add missing ref * ci: trigger db diagram commit * docs(readme): Update Mermaid DB Schema Diagram in README.md (siren-gen) * docs(readme): bring test coverage score up to date * ci: trigger * docs(readme): Update Mermaid DB Schema Diagram in README.md (siren-gen) * docs(readme): bring test coverage score up to date * ci: revert test change --------- Co-authored-by: Aleksandr Shinkarev <ashinkarev@tourmalinecore.com> Co-authored-by: Workflow Action <contact@tourmalinecore.com>
… from the api to be consumed by ui (#49) * ci: try to publish a package in workflow * ci: update node version * ci: update node version * c: fix * c: fix * c: fix * c: fix * chore: remove a part of types from index.ts to test a new workflow * ci: add infra to generate new js client by running api in docker * ci: update publish-js-client-npm-package.yml to test package re-generation with sha version * ci: detached run of the api * ci: try to wrap version in quotes * ci: try to use non sha- version for npm package * ci: try to use partially sem ver with sha adding a flag to ignore git tags creation * ci: add tag for publish because it fails without it * ci: tag without semver part * ci: try to publish to npm registry to avoid the need to use .npmrc with a token which is too much for a publicly available api client * ci: try trusted publishers oidc instead of a custom access token * ci: add .npmignore to avoid index.ts in the package * ci: add git commit step to publish-js-client-npm-package.yml, improve steps * ci: fix publish-js-client-npm-package.yml for PRs and for future push to master * ci: add debug status, comment to speed up * ci: fix permssion to commit, return commented code since it is its results making git working tree not clean * ci: git add all needed changed files * chore(js-client): Update js-client by OpenAPI [skip ci] * ci: try to test master branch flow using fb name instead * ci: make non sem ver tag for default branch release * ci: temp remove paths * chore(js-client): Update js-client by OpenAPI [skip ci] * ci: improve comments, remove testing of master from db, try to get rid of an argument to see if it is needed * chore(js-client): Update js-client by OpenAPI [skip ci] * ci: improve comments, finalize master branch name * ci: co-locate js-client and its generation code * fix!: use time-api version of operationId generation in the contract so that it is developer friendly and contains controller name and method name * git: add missing thing for concurrent commits from workflows * chore(js-client): Update js-client by OpenAPI [skip ci] * docs(readme): bring test coverage score up to date * ci: test 3 parallel commits * docs(readme): Update Mermaid DB Schema Diagram in README.md (siren-gen) * chore(js-client): Update js-client by OpenAPI [skip ci] * docs(readme): bring test coverage score up to date * ci: rename build to a better job name according to the convention, remove not yet used postfix to avoid confusion * ci: revert db-diagram-generation-on-pull-request.yml * chore(js-client): Update js-client by OpenAPI * ci: not commit changes to version in package.json and package-lock.json, add comment * ci: test change * ci: trigger workflow * ci: try to fix docker-compose.yml * chore(js-client): Update js-client by OpenAPI * Update .github/workflows/publish-js-client-npm-package.yml --------- Co-authored-by: Aleksandr Shinkarev <ashinkarev@tourmalinecore.com> Co-authored-by: Workflow Action <contact@tourmalinecore.com>
…t.yml and trigger deployment (#50) Co-authored-by: Aleksandr Shinkarev <ashinkarev@tourmalinecore.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.