Skip to content

Actions: hackerb9/tokenize

Actions

release

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
38 workflow runs
38 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Microsoft Windows lacks /dev/stdin, even with bash
release #38: Commit 6e36ebe pushed by hackerb9
July 17, 2024 08:13 1m 3s v2.0.0
July 17, 2024 08:13 1m 3s
Grammar
release #37: Commit 66c450f pushed by hackerb9
July 11, 2024 15:10 1m 14s v1.2.0
July 11, 2024 15:10 1m 14s
Only release a new version if the tag pushed == v*.*
release #36: Commit b5d68e0 pushed by hackerb9
March 23, 2024 00:35 1m 1s v1.1.3
March 23, 2024 00:35 1m 1s
Try without if: startsWith(github.ref, 'refs/tags/')
release #35: Commit 88a8f8f pushed by hackerb9
March 20, 2024 09:34 28s macos-build
March 20, 2024 09:34 28s
Just use gcc since cc is not found on GitHub's MS Windows
release #34: Commit 1f54fea pushed by hackerb9
March 20, 2024 09:23 1m 42s macos-build
March 20, 2024 09:23 1m 42s
Ugh, why does Windows Make not like my syntax
release #33: Commit 6e95fb8 pushed by hackerb9
March 19, 2024 23:46 1m 23s macos-build
March 19, 2024 23:46 1m 23s
What do I have to do to change the PATH in Windows?
release #32: Commit 5bbd2b7 pushed by hackerb9
March 19, 2024 23:42 1m 16s macos-build
March 19, 2024 23:42 1m 16s
oops, GitHub Release requires a tag
release #31: Commit 3734ec3 pushed by hackerb9
March 19, 2024 23:38 1m 16s macos-build
March 19, 2024 23:38 1m 16s
distribution should include all *.tar.gz files
release #30: Commit 37cec3b pushed by hackerb9
March 19, 2024 23:37 42s macos-build
March 19, 2024 23:37 42s
Nope, that didn't work. What is the syntax for PATH on Windows?
release #29: Commit 18a71fd pushed by hackerb9
March 19, 2024 23:33 1m 13s macos-build
March 19, 2024 23:33 1m 13s
Try kludging the Windows PATH
release #28: Commit ccd8570 pushed by hackerb9
March 19, 2024 23:30 1m 15s macos-build
March 19, 2024 23:30 1m 15s
What about tricking windows with double quotes?
release #27: Commit 05dd4fb pushed by hackerb9
March 19, 2024 23:23 1m 14s macos-build
March 19, 2024 23:23 1m 14s
Okay, gcc worked on Windows, but why?
release #26: Commit bf0ec77 pushed by hackerb9
March 19, 2024 23:18 1m 17s macos-build
March 19, 2024 23:18 1m 17s
which cc is windows running? or is it running one at all?
release #25: Commit bcc7d1a pushed by hackerb9
March 19, 2024 23:12 1m 25s macos-build
March 19, 2024 23:12 1m 25s
why is cc not in the path on MS Windows?
release #24: Commit b857f30 pushed by hackerb9
March 19, 2024 23:03 55s macos-build
March 19, 2024 23:03 55s
Where does win_flex write its output?
release #23: Commit b4cebee pushed by hackerb9
March 19, 2024 22:57 1m 11s macos-build
March 19, 2024 22:57 1m 11s
Try ifeq(${OS}, Windows_NT)
release #22: Commit db9cb43 pushed by hackerb9
March 18, 2024 19:55 1m 22s macos-build
March 18, 2024 19:55 1m 22s
what is the output of windows uname
release #21: Commit 880167c pushed by hackerb9
March 18, 2024 19:47 1m 38s macos-build
March 18, 2024 19:47 1m 38s
Windows special casing
release #20: Commit 0edc203 pushed by hackerb9
March 18, 2024 11:09 1m 27s macos-build
March 18, 2024 11:09 1m 27s
Add MacOS brew path for GNU tar
release #19: Commit 45de380 pushed by hackerb9
March 18, 2024 10:52 1m 24s macos-build
March 18, 2024 10:52 1m 24s
OS independent .tar.gz files for 'make artifacts'
release #18: Commit 1e9860f pushed by hackerb9
March 18, 2024 10:40 50s macos-build
March 18, 2024 10:40 50s
Virtualized MacOS doesn't like me writing to /dev/stdout
release #17: Commit 80269df pushed by hackerb9
March 18, 2024 10:13 1m 14s macos-build
March 18, 2024 10:13 1m 14s
chocolatey for Windows
release #15: Commit c02db7e pushed by hackerb9
March 18, 2024 09:59 45s macos-build
March 18, 2024 09:59 45s
make for each os
release #14: Commit 2377c41 pushed by hackerb9
March 18, 2024 09:51 52s macos-build
March 18, 2024 09:51 52s