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.

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

SEMANTIC-RELEASE - Add semantic release #75

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

dmitrif
Copy link
Collaborator

@dmitrif dmitrif commented May 11, 2021

  • Migrates release process to use Semantic-release
  • TODO: Add docs specifying the need for github-app-installation-token-action

@dmitrif dmitrif force-pushed the SEMANTIC-RELEASE branch from 6b08820 to d5aacbf Compare May 11, 2021 15:31
@dmitrif dmitrif force-pushed the SEMANTIC-RELEASE branch from d5aacbf to d59e138 Compare May 11, 2021 15:33
@gagoar gagoar self-requested a review May 11, 2021 22:59
@codecov-commenter
Copy link

Codecov Report

❗ No coverage uploaded for pull request base (main@9a6548c). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main      #75   +/-   ##
=======================================
  Coverage        ?   38.09%           
=======================================
  Files           ?        7           
  Lines           ?       42           
  Branches        ?        2           
=======================================
  Hits            ?       16           
  Misses          ?       26           
  Partials        ?        0           
Flag Coverage Δ
unittests 38.09% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9a6548c...08912fa. Read the comment docs.

@gagoar
Copy link
Owner

gagoar commented Jan 11, 2022

could you rebase? I've done some changes in the underlying workflows! thanks!

@dmitrif
Copy link
Collaborator Author

dmitrif commented Jan 18, 2022

@gagoar Heyo! What should ORG_PRIVATE_KEY point to? Thanks!

@gagoar
Copy link
Owner

gagoar commented Jan 19, 2022

@gagoar Heyo! What should ORG_PRIVATE_KEY point to? Thanks!

I will add the value so you can use it. I need to generate one for particular use. ping you when is set.

@dmitrif
Copy link
Collaborator Author

dmitrif commented Mar 24, 2022

@gagoar Heyo! Just wanted to follow-up re: above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants