feat: Begin transition from DevOps to GHA#11
Conversation
|
Hey @BenjaminMichaelis do you think we can try building without Arcade? I opted out of using it on my machine as Jon said that we actually don't need it as that was an internal requirement for the OG version, and seemingly I can build without it just fine. |
…o-gha-plan Migrate from Azure Pipelines to GitHub Actions
Consolidate CI build jobs with matrix strategy
…ching-simplification Simplify npm caching in build-and-test action
…igate-failures fix: resolve form input race and clean up GHA Arcade references
…peline-alignment ci: align GHA pipeline parity with legacy behavior
…-non-ci-changes chore: revert non-CI changes from main branch
|
@sassdawe totally forgot to mention, I can't trigger workflows so going a bit blind here, but I think we should review, then merge, and iterate on any issues we see. Thoughts? I am having the workflows run on my fork though - prior to the merge, the CI ran: https://github.com/BenjaminMichaelis/interactive/actions/runs/26665445807/job/78597690923 After the latest merge it looks like though it is failing: https://github.com/BenjaminMichaelis/interactive/actions/runs/29498556169/job/87621356663#step:4:194 |
|
Hey, I'm trying to bring your work over to my fork but somehow I managed to commit into yours. Git is confusing...
I want to build and test in my fork before we merge into the original but as you can see I'm having a steep learning curve here 😅
…________________________________
From: Benjamin Michaelis ***@***.***>
Sent: Thursday, 16 July 2026 17:30:27
To: Polyglossy/interactive ***@***.***>
Cc: David Sass ***@***.***>; Mention ***@***.***>
Subject: Re: [Polyglossy/interactive] feat: Begin transition from DevOps to GHA (PR #11)
[https://avatars.githubusercontent.com/u/22186029?s=20&v=4]BenjaminMichaelis left a comment (Polyglossy/interactive#11)<#11 (comment)>
@sassdawe<https://github.com/sassdawe> totally forgot to mention, I can't trigger workflows so going a bit blind here, but I think we should review, then merge, and iterate on any issues we see. Thoughts? I am having the workflows run on my fork though - prior to the merge, the CI ran: https://github.com/BenjaminMichaelis/interactive/actions/runs/26665445807/job/78597690923
After the latest merge it looks like though it is failing: https://github.com/BenjaminMichaelis/interactive/actions/runs/29498556169/job/87621356663#step:4:194
—
Reply to this email directly, view it on GitHub<#11?email_source=notifications&email_token=ACSBVTPJ5QIS4BQTBXX3QOD5FDYI7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJZGM3DSMRWGI2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4993692624>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACSBVTJL2PMIZ643VH3IR6D5FDYI7AVCNFSNUABGKJSXA33TNF2G64TZHMYTEMZVGU3TQNZYGY5US43TOVSTWNBUGYZDONZVHA3TBILWAI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I totally broke the package-lock files when I was trying to reconcile the merge conflicts here: sassdawe#23 |
|
@BenjaminMichaelis I am in the process of cherry picking these three files, so I can test them without anything else:
I believe you'll need to create another branch with nothing else changed just these files and submit a PR from that branch. |
|
@sassdawe I have just dropped the merge out of this pr! |
I took your changes with minimal changes to produce cleaner history: FEAT: (GH Actions) CI and Release pipelines |
3 participants
WIP - some high level attempts at getting the GHA pipelines started
This pull request introduces a comprehensive overhaul of the project's CI/CD automation and dependency management. It adds new GitHub Actions workflows for continuous integration and publishing, establishes a composite action for standardized build and test steps across platforms, and sets up automated dependency updates for GitHub Actions, npm, and NuGet packages. These changes modernize and streamline the project's automation, making builds, tests, and releases more reliable and maintainable.
CI/CD Workflow Automation:
.github/workflows/ci.ymlworkflow to handle continuous integration on both Windows and Linux, including branch and path filters, artifact uploads, and improved concurrency handling..github/workflows/publish.ymlworkflow to automate the release process, including building, testing, packaging, and publishing to NuGet, npm, and the VSCode Marketplace, with support for dry-run simulations and proper environment gating.Reusable Build and Test Logic:
.github/actions/build-and-test/action.ymlto encapsulate cross-platform build and test logic, including caching, environment setup, and platform-specific steps for both Windows and Linux.Automated Dependency Management:
.github/dependabot.ymlconfiguration to enable Dependabot for GitHub Actions, npm, and NuGet, ensuring dependencies are kept up to date automatically with grouped updates and appropriate labeling.Miscellaneous:
Directory.Build.targets.