Incompatible with non-git repositories

[meskill]

This is a rare case, especially when using GitHub, but there are options to use VCS other than git, e.g. Jujutsu. But gh-workflow relies on the git repository and git binary available here

gh-workflow/src/generate.rs

Lines 37 to 42 in 11be623

	let root_dir = String::from_utf8(
	Command::new("git")
	.args(["rev-parse", "--show-toplevel"])
	.output()?
	.stdout,
	)?;

Consider using other approaches to find proper root to put the workflow files. Maybe https://github.com/azzamsa/toor could be helpful

[tusharmath]

Should be a simple change. Feel free to raise a PR.

[simonsan]

cargo metadata has the field: workspace_root, this could be of help, I think.

https://docs.rs/cargo_metadata/0.19.0/cargo_metadata/

Though thinking about it, this would bind it to a repository containing a cargo project, not sure if that is wanted. 😅

[tusharmath]

Thanks @simonsan. Toor is designed just to find the root. If it's not a very large library we should go ahead.

[simonsan]

Thanks @simonsan. Toor is designed just to find the root. If it's not a very large library we should go ahead.

I think it's not worth it to pull in a library with 2k downloads and with the insecurity of being maintained any further, the logic is just a few LOC.

https://github.com/azzamsa/toor/blob/master/src/project.rs

Essentially, it looks for some hardcoded patterns in the directories, goes to the parent. I think that could be boiled down to a 3-5 LOC. That being said, you probably want to have a way to determine a repository based on the ability of the .github/workflows directory?