This check required the new type of +type to nest within the old type of
+type, which is wrong. Specifically, this disallowed adding new runes
without a staging procedure (which we didn't successfully complete).
* jt-gall-refactor: (76 commits)
gall: fix issue id in comment
pills: update solid
gall: handle foreign coup success
gall: only print peek bad result if bad
gall: add basic test harness
pills: update solid, brass, ivory
gall: fix obvious nest-failing tisdot
gall: change '-state' to '-core' for +mo and +ap
zuse, gall: deprecate 'club'
zuse, gall, eyre: deprecate 'cush'
zuse, gall, eyre, dojo: deprecate 'cuft'
gall: remove slam-related printfs
gall: remove deprecated 'mak' from 'agents'
gall: use less vertical spacing throughout
gall: add comment re: unpopulated wex
gall: use less vertical separation when wuthepping
gall: fix whitespace
gall: don't define 'move' as a pair
gall: don't give faces to tags
gall: gut some unused stuff
...
Edit post's UI appearance looked quite different
from what creating a new post looked like.
This commit just brings the styling of post
editing UI a bit closer together with new posts.
* origin/chat-style:
Added another round of changes
Broke out functions, inlined more of the app, fewer declarations, more subject modifications rather than subject additions
Added more changes.
Updated to remove some of the =/ with the old style, and a few other small changes
Added fixes to chat style as per Mark's comments
Signed-off-by: Jared Tobin <jared@tlon.io>
gulp.rename just copies files, leaving the original.
For minified files, this was navigated by not
tracking the -min.js files in git. However, when
deploying OTA, the -min.js files are still deployed
to all ships. This commit adds 'del' package,
and a task to clean up the -min files when done
for all current Landscape applications.
'Urbit' refers to the project/product/platform, whereas 'urbit' refers
to an individual ship or instance. This corrects some old, incorrect
lower-case usage.
Revamps the "Git practice" section to make it less of a git and GitHub
tutorial and more of a guide of expected contribution style. In
particular, it answers the questions of:
* what tree contributors should branch from
* how to submit contributions
* how to structure commits
* how to format commit descriptions
* what contributions are considered acceptable
* what our expectations are around committing pills
Additionally, adds a "Releases" section that describes how we go about
making and deploying releases.
