ProwlEngine / ProwlEngine/Prowl
[Editor] Docker/container image
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 120
- Avg merge
- 11h 28m
- Merged PRs (30d)
- 11
Description
Imagine users creating their one games using Prowl and every time they commit, GitHub/GitLab would automatically build the executables for Windows/Mac/Linux. Cool right? It's done using containers.
Tasks:
- (prerequisite) Implement local
buildcommand line from #151 - certify that, even on Linux, it's possible to build a project to a Windows target
- add a new GitHub action at
.github/workflowsto create the containers with tagslatestandvX.X,X
IMPORTANT
Unlike just building and testing (that are done on every commit), the container creation should be only onmainand/or releases. Consider implementing a release routine, even in the "beta" stage.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking prerequisite issue #151 for the local build command, then review the existing .github/workflows setup and the project’s Windows, Mac, and Linux build targets. Done means Linux can produce a Windows target, container images are tagged latest and vX.X.X, and creation runs only on main and/or releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, docker, github-actions
- Domain
- build-system, ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100