A Dev Flow for Google App script. Starter templates, a label scheme, the presentation with many links for reading further, a list of what to install and what it might cost you.
This repo will be used to demonstrate the described 'development work flow' for creating and maintaining google app script. It will be updated over time to demonstrate various best practices and general demonstrations; some inspired by topics covered in the Totally Unscripted series and posts in the over 20,000 member strong G+ Google Apps Script Community and others by my own private projects.
v0.1.0 "empty shell" - the basic repository with .github folder of templates for contributing, issues, and pull requests and without code
v0.2.0 "namespace w semantic versioning" - a few files to establish .gs namespace for our work
v1.0.0 "minimal addon for sheets" - Demonstrable, can clone and publish test as addon; a basic sidebar and at least one function to demonstrate changes, workflow start and restart
v1.1.0 "what's new" - the what's new approach from earlier TU Episode
v1.2.0 "make test ready" - automation of applying naming standards during script development and sheets testing
v1.3.0 "tbd" - open for suggestions
- Star and watch this repo for ongoing updates
- Install ZenHub extension in Chrome or Firefox from the GitHub Marketplace
- Use the ZenHub task board to monitor flow of issues and to add to the discussion
- Follow contributing guidelines for adding new issues like requests for demos or your own idea
- Follow 'git flow' conventions for proposing new code; see git flow documentation; i recommend using GitKraken
My 7m presentation is followed by about 7 min of discussion. Check out the whole episode if you have time.
Our contributing guidelines in code repo file "DevFlow/.github/CONTRIBUTING.md" or from link when opening a new issue
“A Successful Git branching model” by Vincent Driessen
“Better Software & Stronger Teams: Project Management for GitHub” by By Matt Butler and Paige Paquette of ZenHub
“Comparing Workflows” by Atlassian
“Make The Product Backlog DEEP” by Roman Pichler
“Post-Agile: A Design Thinking Approach to Software Development” by Tom Dabson
“Semantic Versioning” by Tom Preston-Werner
GitHub - Remote Origin or “truth” repo hosted on private or public repository. With the following standards:
-Git Flow - branch and release tagging approach; see reading list and also GitKraken; enables scalable workflow as you add developers and repositories.
-Semantic Versioning 2.0.0 - referred to and modified in creating our own, consistently applied approach during development and for live releases. Tied to our analytics, release tagging, and code changes.
ZenHub - integrates natively with GitHub's user interface providing a layer of planning without context switching; burndown charts, Velocity tracking, and Release reports powered by live GitHub data. Keeps more people closer to the code.
Atom - hackable text editor for Windows, Mac AND Linux.
GitKraken - Git GUI for Windows, Mac AND Linux. Free for open source, educational, non‑profit, or personal use.
G Drive Script editor - best in Chrome
GAS Github Assistant - Chrome extension
Google accounts are separate.
| Tool | Free | Paid |
|---|---|---|
| 1 GitHub | public repos | $7/m Developer 25/m Org team w/ first 5 more at 9per |
| 2 ZenHub | < 6 people | $5 user/m on 6 or more |
| 3 Atom | open source | open source |
| 4 GitKraken | sometimes w/o conflict tool | 49/yr Ind user 390/yr 10 users |
| 5 Script Editor with 6 GAS GH Assistant | open source | open source |
| Total | 0 | Affordable : ) |
It is possible to install and run some releases of Linux on a Chromebook that's been put into Developer mode.
Please see "crouton" - Chromium OS Universal Chroot Environment
The cool part here is that you are not dual booting and the Chromebook appears to receive updates and continues to support multiple users. I'm told this voids the warranty on the Chromebook? Worth exploring.