Replies: 3 comments 1 reply
-
My apologies if you are watching all activity of the repo, I have unwillingly spammed your email box with all the failed releases. Even though I created a separate repo to develop and test the releases, I still had to make some iterations in this repo to get it right (e.g in new repos, the "base" branch is called main instead of master). |
Beta Was this translation helpful? Give feedback.
-
LOL, I don't mind!
…On Wed, Jan 11, 2023 at 4:41 PM David Buezas ***@***.***> wrote:
My apologies if you are watching all activity of the repo, I have
unwillingly spammed your email box with all the failed releases have. Even
though I created a separate repo to develop and test the releases, I still
had to make some iterations in this repo to get it right (e.g new repos
master as main).
I think everything is setup right now, so the unwanted emails should stop
now.
—
Reply to this email directly, view it on GitHub
<#229 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACPEX7C77JB5VVFYW2ZRFDLWR4SI3ANCNFSM6AAAAAATYGXOYI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
No problem and thanks to all for all the hard work. Much appreciated. |
Beta Was this translation helpful? Give feedback.
-
Apologies for disattending the pull requests for so long.
I am now introducing automatic releases each time a PR is merged into the repository.
@LaZsolt, I registered as collaborator 🎉 . This should also allow you to merge Pull Requests.
Each time a PR is merged the release action will be triggered, which does the following
lgt8f-1.0.x.zip
file)package_lgt8fx_index.json
file with the new versionExcept for PRs that only change the
readme.md
file, or files inside/docs
. Those won't generate a release.This means that there will be one release for each PR, so let's avoid merging a PR that is not fully functional.
Beta Was this translation helpful? Give feedback.
All reactions