We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create an .sh with commented output lines for # status and # log
# status
# log
Objectives
diff
pyrpo.rebuild-full.sh
Output:
### [pyrpo commandline] ## hostname ## datetime ## <path> git clone <url> <path> git remote add/remove/update <./path> <url> # status # logs ## </path>
Current Support
pyrpo -r sh
pyrpo -r status
pyrpo -r full
Questions
Would it make sense to store this in a repository?
Sort of. status and output likely differ from environment to environment
status
output
TODO
Pick and implement {GitRev, HgRev, ...} __str__ syntax
GitRev
HgRev
__str__
Add an sh_full report + option
sh_full
Add a default option and/or output filepath for these types of reports
(--sh-full, --sh-rebuild, --awesome)
--sh-full
--sh-rebuild
--awesome
Prefix status lines with #
#
Prefix log lines (split by \n) with #
\n
Add a commented commandline args + hostname header
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Create an .sh with commented output lines for
# status
and# log
Objectives
diff
-ablepyrpo.rebuild-full.sh
reportsOutput:
Current Support
pyrpo -r sh
pyrpo -r status
pyrpo -r full
Questions
Would it make sense to store this in a repository?
Sort of.
status
andoutput
likely differ from environment to environmentTODO
Pick and implement {
GitRev
,HgRev
, ...}__str__
syntaxAdd an
sh_full
report + optionAdd a default option and/or output filepath for these types of reports
(
--sh-full
,--sh-rebuild
,--awesome
)Prefix status lines with
#
Prefix log lines (split by
\n
) with#
Add a commented commandline args + hostname header
The text was updated successfully, but these errors were encountered: