setup-msys2
roadmap
setup-msys2 | roadmap | |
---|---|---|
2 | 67 | |
268 | 7,709 | |
4.5% | 0.6% | |
7.0 | 0.0 | |
1 day ago | 23 days ago | |
JavaScript | ||
MIT License | Creative Commons Attribution 4.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
setup-msys2
-
Getting Started with Git Bash
Other pages provide complementary information on that same topic.
Another thing I appreciated was the explanation of MSYS2's environments:
https://www.msys2.org/docs/environments/
Being able to painlessly switch away from MSVCRT to UCRT was helpful in solving some UTF-8 difficulties I was experiencing at the time.
Package management with pacman is rather pleasant, and the setup-msys2 GitHub Action makes it simple to provide your GHA workflow with the tools and libs you want:
https://www.msys2.org/docs/package-management/
https://packages.msys2.org/queue
https://github.com/msys2/setup-msys2
-
GitHub Actions by Example
> Actions reduce workflow steps by providing reusabe[sic] “code” for common tasks. To run an action, you include the uses keyword pointing to a GitHub repo with the pattern {owner}/{repo}@{ref} or {owner}/{repo}/{path}@{ref} if it’s in a subdirectory. A ref can be a branch, tag, or SHA.
Aside from the typo, I wonder how many packages could be backdoored at once, if an action maintainer went rogue, seeing as there's no pinning for actions by default, and (according to https://github.com/msys2/setup-msys2/blob/main/HACKING.md) moving a tag is the default way to push updates to an action. (Interestingly get-cmake/run-cmake/run-vcpkg are all operated by the same person.)
roadmap
- GitHub: Packages support for fine-grained PATs
- Microsoft cancels plans for Python packages on GitHub
-
Github will unfortunately not provide a helm repository in the future.
Same message as for PyPI compatible package registry: https://github.com/github/roadmap/issues/94
-
GitHub support for PHP Packages: “no longer planned”
Yeah I had to look around a bit but yep… https://github.com/github/roadmap/issues/94
It looks like a lot of things have been killed… which with my cynical hat on I think might have something to do with overlapping capabilities with Azure services.
- GitHub Packages no longer planning Python PyPI support
-
How do you debug CI/CD pipelines? Breakpoints?
Others have mentioned tmate to SSH into a running GitHub Actions workflow; there is a roadmap issue making that functionality built-in to Actions, planned for 2023/Q4.
-
GitHub Actions is Vulnerable to Supply Chain Attacks
Immutable actions are on GitHub's roadmap.
- How to manage large GitHub orgs?
-
Which role does Github Actions currently play in MLOps?
I think not yet, but seems to be in the roadmap
- Developing for M1/M2 without a Mac
What are some alternatives?
WSL - Issues found on WSL
plantuml - Generate diagrams from textual description
tip - GitHub Action to keep a 'tip' pre-release always up-to-date
trufflehog - Find and verify secrets
toast - Containerize your development and continuous integration environments. 🥂
act - Run your GitHub Actions locally 🚀
dependabot-sha-comment-ac
gitlab
github-script - Write workflows scripting the GitHub API in JavaScript
dependabot-core - 🤖 Dependabot's core logic for creating update PR's.
github-actions-ensure-sha-pinne
xmonad - The core of xmonad, a small but functional ICCCM-compliant tiling window manager