zombocom / rundoc Goto Github PK

== Running your docs
Running: email = ENV['HEROKU_EMAIL'] || `heroku auth:whoami`
Rundoc.configure do |config|
  config.project_root = "myapp"
  config.filter_sensitive(email => "[email protected]")
end
Running: $ 'ruby -e "exit 1 unless RUBY_VERSION == '2.6.6'"'
Running: $ 'gem install rails --no-document'
Running: $ 'rails new myapp --database=postgresql'
running $ cd myapp
Running: $ 'bin/rails db:create'
Running: $ 'cat config/database.yml'
Running: $ 'rails generate controller welcome'
Writing to: 'app/views/welcome/index.html.erb'
Writing to: 'config/routes.rb' line 2 with: "  root 'welcome#index'\n"
Running: $ 'sed -i'' -e '/^ruby/d' ./Gemfile'
Writing to: 'Gemfile' line 4 with: "ruby \"2.6.6\"\n"
Running: $ 'git --help'
Piping: results of '$ git --help' to '#<Rundoc::CodeCommand::Bash:0x00007fb395259d10>'
Running: $ 'head -n 5' with stdin: '"usage: git [--version] [--help] [-C <path>] [-c <name>=<value>]\n           [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]\n           [-p | --paginate | -P | --no-pager] [--no-replace-objects] [--bare]\n           [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]\n           <command> [<args>]\n\nThese are common Git commands used in various situations:\n\nstart a working area (see also: git help tutorial)\n   clone             Clone a repository into a new directory\n   init              Create an empty Git repository or reinitialize an existing one\n\nwork on the current change (see also: git help everyday)\n   add               Add file contents to the index\n   mv                Move or rename a file, a directory, or a symlink\n   restore           Restore working tree files\n   rm                Remove files from the working tree and from the index\n   sparse-checkout   Initialize and modify the sparse-checkout\n\nexamine the history and state (see also: git help revisions)\n   bisect            Use binary search to find the commit that introduced a bug\n   diff              Show changes between commits, commit and working tree, etc\n   grep              Print lines matching a pattern\n   log               Show commit logs\n   show              Show various types of objects\n   status            Show the working tree status\n\ngrow, mark and tweak your common history\n   branch            List, create, or delete branches\n   commit            Record changes to the repository\n   merge             Join two or more development histories together\n   rebase            Reapply commits on top of another base tip\n   reset             Reset current HEAD to the specified state\n   switch            Switch branches\n   tag               Create, list, delete or verify a tag object signed with GPG\n\ncollaborate (see also: git help workflows)\n   fetch             Download objects and refs from another repository\n   pull              Fetch from and integrate with another repository or a local branch\n   push              Update remote refs along with associated objects\n\n'git help -a' and 'git help -g' list available subcommands and some\nconcept guides. See 'git help <command>' or 'git help <concept>'\nto read about a specific subcommand or concept.\nSee 'git help git' for an overview of the system.\n"'
Running: $ 'ls'
Running: $ 'git init'
Running: $ 'git add .'
Running: $ 'git commit -m "init"'
Running: $ 'git status'
Running: $ 'heroku create'
Running: $ 'git config --list | grep heroku'
Running: $ 'git push heroku main'