Skip to content

Latest commit

 

History

History
60 lines (46 loc) · 2.14 KB

DEVELOPMENT.md

File metadata and controls

60 lines (46 loc) · 2.14 KB

Development

fix.sh

If you want to use rbenv/pyenv/etc to manage versions of tools, there's a fix.sh script which may be what you'd like to install dependencies.

Overcommit

This project uses overcommit for quality checks. bundle exec overcommit --install will install it.

direnv

This project uses direnv to manage environment variables used during development. See the .envrc file for detail.

Run Chrome extension from local checkout

  1. Run 'make' to create the bundle with webpack, or 'make start' to start webpack in watch mode.
  2. Go to chrome://extensions/
  3. Make sure 'Developer mode' is flipped on in the upper right.
  4. Click the 'Load unpacked' button.
  5. Choose the dist/chrome-extension directory

Testing changes

  1. make
  2. Head to 'wip-limiter-example' project and verify each appears as described in section header.
  3. Head to your 'My Tasks' page and set up WIP limits to test.
  4. Go into a task and set up WIP limits to test.

Releasing to Chrome Web Store

  1. Update screenshots in docs/ for any new features
  2. Update README.md with new screenshots
  3. PR screenshot updates in
  4. git stash && git checkout main && git pull
  5. Bump the version in static/chrome-extension/manifest.json locally. 1.git commit -m "Bump version" static/chrome-extension/manifest.json
  6. git push && make clean && make
  7. Update package.zip in developer dashboard as apiology-cws user.
  8. Upload any new screenshots
  9. Update description to match current README.md - manually translate from markdown to text.
  10. Save draft
  11. ... | Preview
  12. Publish

Installing local version

  1. Run 'make' to create the bundle with webpack, or 'make start' to start webpack in watch mode.
  2. Go to chrome://extensions/
  3. Make sure 'Developer mode' is flipped on in the upper right.
  4. Click the 'Load unpacked' button.
  5. Choose the dist directory