GitHub Actions Workflow Improvements
See original GitHub issueThere are some elements in our CI that can be improved:
For example, code-style.yml
starts very often in non-code updates. The same for docs.yml
for non-docs.
pytorch-version-tests.yml
fails to open the issue because of access problem:
https://github.com/pytorch/ignite/runs/2157534748?check_suite_focus=true#step:9:8
- code-style
- docs
- unit-tests: https://github.com/pytorch/ignite/pull/1838#issuecomment-804796165
Issue Analytics
- State:
- Created 3 years ago
- Comments:9
Top Results From Across the Web
Features • GitHub Actions
Built in secret store. Automate your software development practices with workflow files embracing the Git flow by codifying it in your repository.
Read more >GitHub Actions: Improvements to reusable workflows
You can now nest up to 4 levels of reusable workflows giving you greater flexibility and better code reuse. Calling a reusable workflow...
Read more >GitHub Actions Performance Improvement for your CI/CD
Therefore, in this article we will learn how can you leverage the GitHub caching workflow dependencies mechanism to improve speed and save ...
Read more >Evolution of GitHub Action Workflows - Alexandre Bergel
This paper presents the result of a manual inspection of 222 commits of GitHub Actions workflows obtained from 10 popular open-source repositories. Our ......
Read more >Evolution of GitHub Action Workflows - IEEE Xplore
GitHub Actions are an event-driven tool to automatically respond to particular ... opportunities for improvement in the way workflows are built and edited....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@vfdev-5 Absolutely, docs is very tricky, docs is tightly connected with the repo code, its hard to find non-docs related parts, I was thinking about reducing the number of docs “dry runs” on pull_request by excluding
docker
, some GHA workflow files,tests
but I think its minor changes, so let’s keep it as it isCan you try that on a separate repo to see what it works exactly. For me “first contribution” is the first and only the first writen issue (same for PR).