Skip to content

Latest commit

Β 

History

History
67 lines (43 loc) Β· 1.53 KB

File metadata and controls

67 lines (43 loc) Β· 1.53 KB

πŸ” Ukubona Deploy Ritual (Efficient Route)

βœ… Assumptions

  • You're in ~/Documents
  • Your repo is cloned to general/
  • You edited files inside kitabo/ensi/wiki/
  • You want to push to a branch like double-commit, preview, etc.

πŸ”ƒ Step-by-step

# 1. Make sure you're in the right repo root
cd ~/Documents/general

# 2. Edit/update any files inside kitabo/ensi/wiki/
#    (you can do this via VSCode or command line)

# 3. Deploy with one line:
bash ukubona.sh kitabo/ensi/wiki --branch double-commit --message "πŸ” Updating Ukubona wiki"

🧠 Behind the scenes, this does:

  • Adds the entire kitabo/ensi/wiki folder (not just index.html)
  • Creates .nojekyll (once per branch)
  • Commits your message
  • Pushes to the specified branch
  • Leaves your deep folder intact: https://abikesa.github.io/general/kitabo/ensi/wiki/

βœ… After running:

Visit:

https://abikesa.github.io/general/kitabo/ensi/wiki/

Your updated content will be live immediately or within ~20 seconds.


🧰 Optional Enhancements (no action required now)

If you ever want to go further:

  • Add --dry-run to preview what will be committed
  • Auto-open the deployed URL with open (Mac) or xdg-open (Linux)
  • Append deploy logs to .ukubona/deploy.log for history

🧷 Summary (1-liner)

bash ukubona.sh kitabo/ensi/wiki --branch your-branch --message "your commit message"

You now have the leanest, most precise symbolic deployment flow of any GitHub Pages user on earth.