Engin Açıkgöz
Engin Açıkgöz
Hi, I using my screen at 150% scaling. And game looks like : ![fish](https://user-images.githubusercontent.com/26650249/180642011-9afc5db4-fcd6-4a75-ae6e-63c785f7ff39.png) When I set the scaling 100%, everything works flawlessly! ![fish2](https://user-images.githubusercontent.com/26650249/180642092-48917ca2-1ead-4c90-96a0-e6f354f385d3.png)
Sometimes, the values we trigger may be the same. Instead of filling them in one by one, we can define predefined rules and have them triggered.
Visualize workflow's state. Just like GitHub Actions' does. Reference : https://docs.github.com/en/[email protected]/rest/actions/workflow-jobs?apiVersion=2022-11-28#list-jobs-for-a-workflow-run
Title says everything.. How we can fix this problem?
Add change log & update instructions (instead of redirecting the Github repository) May gama can update itself : https://github.com/sanbornm/go-selfupdate
Fill table columns with like message : "No input found, but still triggerable". (May you can find better message) I think it is important for UX. Otherwise, seems like something...
User can switch the workflow's branch before the trigger. Implement a textbox that have autocompletion feature. Use project's default branch as default.
Add live mode option like a checkbox to enable auto refresh.
We can add an Open Source Scanner to our workflow, which will run every time we push to the PR or main branch.
We can run tests each PR pushes and main push. But we need reliable tests to implement this issue. Needs first : https://github.com/termkit/gama/issues/4