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

Make publish workflow work based on tag/branch selected #3634

Closed

Conversation

alanwest
Copy link
Member

@alanwest alanwest commented Sep 7, 2022

Adds a ref parameter to the workflow that must be specified when running it. When running the workflow manually, specifying the ref is required. For our releases, we create both a "core" and "non-core" tag at the same SHA, and it doesn't matter which of the two tags you run the workflow with.

Looks like this:

Screen Shot 2022-09-07 at 3 38 30 PM

The nightly build will continue to use main.


There is an alternative we could explore. The pack and publish workflow could be triggered when we draft a new release. If triggered this way, then the workflow would use the SHA of the release. No need to manually run the workflow and type in the tag name.

@codecov
Copy link

codecov bot commented Sep 7, 2022

Codecov Report

Merging #3634 (af80b32) into main (5208ec0) will decrease coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #3634      +/-   ##
==========================================
- Coverage   87.35%   87.34%   -0.01%     
==========================================
  Files         282      282              
  Lines       10132    10132              
==========================================
- Hits         8851     8850       -1     
- Misses       1281     1282       +1     
Impacted Files Coverage Δ
...tation/OpenTelemetryProtocolExporterEventSource.cs 75.00% <0.00%> (-10.00%) ⬇️
...emetry.Api/Internal/OpenTelemetryApiEventSource.cs 73.52% <0.00%> (-5.89%) ⬇️
src/OpenTelemetry/Logs/OpenTelemetryLogger.cs 86.66% <0.00%> (-2.23%) ⬇️
...Telemetry/Internal/SelfDiagnosticsEventListener.cs 97.65% <0.00%> (+0.78%) ⬆️
src/OpenTelemetry/BatchExportProcessor.cs 84.11% <0.00%> (+1.86%) ⬆️
...ZPages/Implementation/ZPagesExporterEventSource.cs 62.50% <0.00%> (+6.25%) ⬆️

@alanwest alanwest marked this pull request as ready for review September 7, 2022 22:45
@alanwest alanwest requested a review from a team September 7, 2022 22:45
@github-actions
Copy link
Contributor

This PR was marked stale due to lack of activity and will be closed in 7 days. Commenting or Pushing will instruct the bot to automatically remove the label. This bot runs once per day.

@github-actions github-actions bot added the Stale Issues and pull requests which have been flagged for closing due to inactivity label Sep 15, 2022
@alanwest alanwest removed the Stale Issues and pull requests which have been flagged for closing due to inactivity label Sep 19, 2022
@github-actions
Copy link
Contributor

This PR was marked stale due to lack of activity and will be closed in 7 days. Commenting or Pushing will instruct the bot to automatically remove the label. This bot runs once per day.

@github-actions github-actions bot added the Stale Issues and pull requests which have been flagged for closing due to inactivity label Sep 27, 2022
@utpilla utpilla removed the Stale Issues and pull requests which have been flagged for closing due to inactivity label Sep 27, 2022
@utpilla
Copy link
Contributor

utpilla commented Sep 28, 2022

Closing this in favor of #3638

@utpilla utpilla closed this Sep 28, 2022
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.

2 participants