Updated GitHub actions #390
Merged
Conversation
This file contains 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
sonomirco
added
the
patch
|
@d3ssy @cesarecaoduro
|
|
|
Sounds good to me. |
|
Good for me
Sent from Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Guido Maciocci ***@***.***>
Sent: Thursday, December 29, 2022 7:16:31 PM
To: GSharker/G-Shark ***@***.***>
Cc: Cesare Caoduro ***@***.***>; Mention ***@***.***>
Subject: Re: [GSharker/G-Shark] Updated GitHub actions (PR #390)
* Happy to remove diagram... i don't remember ever looking at it or making use of it.
* Yes, would like to get rid of alpha releases, also never used.
* Happy to get rid of NetCore 3.1 build target (i don't think we'll make anyone cry 😄 )
* Shall we move to trunk based development instead of gitflow to simplify the whole CI/CD pipeline?
—
Reply to this email directly, view it on GitHub<#390 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGJG6AY3U34JQW2O3YNVU2TWPVCF7ANCNFSM6AAAAAATLZH6FU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
d3ssy
approved these changes
Dec 29, 2022
|
@d3ssy and @cesarecaoduro I made some changes in the ReadMe file and on the events which are hooked and published on Discord. |
|
Great job!
Thanks.
Sent from Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Mirco Bianchini ***@***.***>
Sent: Friday, December 30, 2022 2:42:00 PM
To: GSharker/G-Shark ***@***.***>
Cc: Cesare Caoduro ***@***.***>; Mention ***@***.***>
Subject: Re: [GSharker/G-Shark] Updated GitHub actions (PR #390)
@d3ssy<https://github.com/d3ssy> and @cesarecaoduro<https://github.com/cesarecaoduro>
Made all the changes.
Once we merge all the PRs, we can remove the development branch and start following trank-based development.
The actual checks build and test the solution every time a PR is created or updated in DotNet 3.1.x and 6.0.x.
I thought to keep 3.1.x only for the checks in the meantime, DotNet 7 will be consolidated.
I made some changes in the ReadMe file and on the events which are hooked and published on Discord.
—
Reply to this email directly, view it on GitHub<#390 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGJG6A3WHMU23ORG2J4XJNLWPZKYRANCNFSM6AAAAAATLZH6FU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this? (check all applicable)
Description
This PR updates the GitHub actions.
A new NuGet API Token has been provided; it should fix the error we got with the last deployment.
Related Tickets & Documents
There are no related tickets.
Added tests?
Added to documentation?