Commit e383366b authored by Tomáš Hübelbauer's avatar Tomáš Hübelbauer

Add planned contributions and development log

parent 960eb7de
......@@ -50,3 +50,11 @@ powershell cmd/pre-commit.ps1 || bash cmd/pre-commit.sh
There doesn't see to be a good way to dry-run the pre-commit hook. (`git commit --dry-run` doesn't run it.)
Either invoke `powershell cmd/pre-commit.ps1` directly or use PowerShell ISE or just commit stuff.
## Studying
See `git log` and [development notes](doc/notes.md).
## Contributing
See [planned contributions](doc/tasks.md).
#!/usr/bin/env bash
echo "Hello from WSL?"
echo "See doc/tasks about the planned decision whether to invoke the PowerShell script here or to rewrite it in Bash here"
# Notes
> Development log.
## 2017-12-31
Implemented a draft solution for tracking XML changes in modern Office files format.
`git log` from today will reveal all the struggle because I used `git commit` to test the pre-commit hook for posterity.
# Tasks
> Planned development:
- Extend the pre-commit PowerShell script to process all modern Office files in repository, not just `Title.docx`
- Decide whether to require PowerShell on Unix also or rewrite the PowerShell pre-commit hook in Bash for that
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment