Highlights
- Arctic Code Vault Contributor
- Pro
Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 50 million developers.
Sign upPinned
1,856 contributions in the last year
Activity overview
Contribution activity
December 2020
Created 67 commits in 17 repositories
Created 4 repositories
- propensive/jovian Scala
- propensive/docs.scala-lang HTML
- propensive/dotty Scala
- propensive/scalaone-examples Scala
Opened 26 pull requests in 4 repositories
propensive/fury
16
merged
1
closed
- Don't duplicate module on rename
- Rebuild before install
- Menu commands and model for shading
- Don't duplicate project conflicts
- Try harder to reset terminal state after Fury runs
- Change menu layout
- Use Jovian instead of Fury IO
- Untracked files fix
- Expect version from vent.dev as an Int
- Don't stop when doing tab completions
- Support for `fury layer remote`
- Improve performance of fury layer pull -r
- Match `Mac OS X` for OS
- Fixes #1598
- Don't use uname
- Avoid empty.maxBy when cloning layer
- Try to fix clone of java-multiaddr
scalazone/scala
7
merged
scala/docs.scala-lang
1
open
propensive/contextual
1
merged
Reviewed 2 pull requests in 2 repositories
optics-dev/Monocle 1 pull request
scalazone/scala 1 pull request
Opened 15 issues in 1 repository
propensive/fury
14
closed
1
open
- renaming a module does not delete the old one
- `fury universe projects` shows duplicate project conflicts
- split `layer` into `catalog` and `imports` menus
- `git checkin` thinks there are untracked files when there aren't
- `fury layer clone` has broken
- show list of published layers
- publish nested layers
- facility to prune imports
- recursive layer pull does too many requests
- build does not recognise OS `Mac OS X`
- tab completion on `fury stop` causes it to become unstoppable
- `ImportHasNoRemote` is thrown when trying to update current layer
- don't use `uname` for OS/arch check
- java-multiaddr repo does not seem to contain the right hash
- empty.maxBy occurs when trying to update missing layer