change state of issue e43d29638fa3836087794c669cde18a9, new -> backlog

create new issue e43d29638fa3836087794c669cde18a9
change state of issue 6418c1d923b740057a6138e16664b3c6, new -> backlog
2025-07-26 13:25:48 -06:00 · 2025-07-26 13:25:38 -06:00 · 2025-07-26 13:23:36 -06:00 · 2025-07-26 13:23:30 -06:00
4 changed files with 10 additions and 1 deletions
--- a/6418c1d923b740057a6138e16664b3c6/description
+++ b/6418c1d923b740057a6138e16664b3c6/description
@ -1,4 +1,4 @@
-add `ent modify ISSUE CHANGE...
+add `ent modify ISSUE CHANGE...`
 CHANGE is one or more changes to make to the issue, that looks a bit
 like the FILTER of `ent list`.  Something like:
--- a/6418c1d923b740057a6138e16664b3c6/state
+++ b/6418c1d923b740057a6138e16664b3c6/state
@ -0,0 +1 @@
 backlog
--- a/e43d29638fa3836087794c669cde18a9/description
+++ b/e43d29638fa3836087794c669cde18a9/description
@ -0,0 +1,7 @@
 add a Workflow section to the README
 This section will describe the typical workflows that ent does well.
 This was one thing i found lacking when investigating alternative issue
 tracking systems before starting ent, and i think doing this well could
 help people start using ent.
--- a/e43d29638fa3836087794c669cde18a9/state
+++ b/e43d29638fa3836087794c669cde18a9/state
@ -0,0 +1 @@
 backlog
Author	SHA1	Message	Date
Sebastian Kuzminsky	1160ad7f08	change state of issue e43d29638fa3836087794c669cde18a9, new -> backlog	2025-07-26 13:25:48 -06:00
Sebastian Kuzminsky	6db4620c67	create new issue e43d29638fa3836087794c669cde18a9	2025-07-26 13:25:38 -06:00
Sebastian Kuzminsky	f1069061cd	change state of issue 6418c1d923b740057a6138e16664b3c6, new -> backlog	2025-07-26 13:23:36 -06:00
Sebastian Kuzminsky	f5f01cb0da	edit description of issue 6418c1d923b740057a6138e16664b3c6	2025-07-26 13:23:30 -06:00