profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/dpaez/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Diego dpaez @geut La Plata, Buenos Aires http://dpaez.github.io/ aka: deka, dk // @geut co-founder / Patagonia's original / Code with opinions. Always.

datproject/comm-comm 88

Community Communication

datproject/project-updates 29

updates from the various projects working on or with dat

dpaez/gyes 7

A plusultra client. It handles real-time multimodality interaction on web applications.

dpaez/choo-the-lil-fw 4

Breve introducción a choo

dpaez/async-tour 2

A hybrid talk/workshop about callbacks, promises and async/await.

dpaez/AirPointerDriver 0

An air gestures modality driver for the plusultra platform.

dpaez/choo-issue-demo 0

temporal demo

dpaez/choo-md-editor 0

Markdown Editor built with Choo / for Choo.

dpaez/cli 0

The Hypergraph Command Line Interface

dpaez/CommunityJSData 0

The actual data for CommunityJS.org

issue closedgeut/chan

`chan gh-release <semver>` doesn't work with `GITHUB_TOKEN` defined

Sorry for the noise 😢 , I'm just trying to get chan set up in GitHub Actions with a project I'm managing and I'm running into small issues.

Current behavior

 λ unset GITHUB_TOKEN
 λ chan gh-release 0.1.3
[chan] [gh-release] › ℹ  info      Uploading GitHub release...

 λ export GITHUB_TOKEN=<REDACTED>
 λ chan gh-release 0.1.3
[chan] [gh-release] › ℹ  info      Uploading GitHub release...
[chan] [gh-release] › ✖  error     TypeError: Cannot read property 'createRelease' of undefined
    at createGithubRelease (file:///Users/mbianchi/workspace/dev/dotfiles/config/yarn/global/node_modules/@geut/chan/src/commands/gh-release.js:84:26)
    at Object.handler (file:///Users/mbianchi/workspace/dev/dotfiles/config/yarn/global/node_modules/@geut/chan/src/commands/gh-release.js:55:9)

The usage of GITHUB_TOKEN is causing an error of the createRelease command, though I can't figure out why. The usage in gh-release looks correct, but maybe something isn't set properly in the data object.

closed time in 3 hours

michaeldbianchi

issue commentgeut/chan

`chan gh-release <semver>` doesn't work with `GITHUB_TOKEN` defined

Closed with #68

New release out: v3.2.2

michaeldbianchi

comment created time in 3 hours

release geut/chan

v3.2.2

released time in 3 hours

push eventgeut/chan

Diego Paez

commit sha e67c04c956e3d6905c8d6b6d34fa5355c6c4c450

v3.2.2

view details

push time in 3 hours

created taggeut/chan

tagv3.2.2

A Changelog CLI based on http://keepachangelog.com/

created time in 3 hours

push eventgeut/chan

Diego Paez

commit sha 189be33b60dbfb53b5ff67c20679aa1309a17889

Update: changelog

view details

push time in 3 hours

push eventgeut/chan

Michael Bianchi

commit sha 45bd2d8b280f31e55003026a05fe903076119829

fix: reference correct octokit action for creating release (#68) * fix: reference correct octokit action for creating release * Add changelog entry for gh-release fix

view details

push time in 4 hours

PR merged geut/chan

fix: reference correct octokit action for creating release

Hello! This is for a fix for creating GitHub releases (#67 )

What I've done:

  1. Updated octokit command for createRelease
  2. Verified no existing tests have regressed
lerna success run Ran npm script 'lint' in 6 packages in 6.8s:
lerna success - @geut/chan-core
lerna success - @geut/chan-stringify
lerna success - @geut/chan
lerna success - @geut/chast
lerna success - @geut/git-url-parse
lerna success - @geut/remark-chan
  1. Verified new code creates release successfully
 λ npm link
 λ chan added "New chan release"
[chan] [added] › ✔  success   Added new changes on your changelog.
 λ chan release 0.1.4
[chan] [release] › ✔  success   New release created. 0.1.4
 λ export GITHUB_TOKEN=<REDACTED>
 λ chan gh-release 0.1.4
[chan] [gh-release] › ℹ  info      Uploading GitHub release...
[chan] [gh-release] › ✔  success   GitHub release created.

What I did not do:

  1. Write new tests to validate this behavior 😞 - I really have no idea how I would do that here in js
+3 -1

2 comments

2 changed files

michaeldbianchi

pr closed time in 4 hours

pull request commentgeut/chan

fix: reference correct octokit action for creating release

Hi @michaeldbianchi this looks great. Thanks for the PR!

Would you mind adding a new changelog entry? Can be something like this:

chan fixed 'reference correct octokit action for creating release #67'

Thanks!

michaeldbianchi

comment created time in 6 hours

issue commentgeut/chan

Allow for non-zero exit code

Hi @michaeldbianchi 👋

This is a valid and good feature in my opinion. Right now we are just logging the error but we can do more and add the exit code as you mention.

If you feel motivated, a PR is welcomed. I think, from a quick look, that adding the right process.exit(code) to the different commands can be a good start.

michaeldbianchi

comment created time in a day

startedgeut/staty

started time in a month

startedjackyzha0/portal

started time in a month

push eventgeut/permanent-seeder

Diego Paez

commit sha 063c861871956b7e07b48ba93b7f401a838aec14

Update: version bump

view details

Diego Paez

commit sha f9ec3568383225a1ba53a6fdfa21d370bc20fa33

Update: changelog

view details

Diego

commit sha 0997911b1dcc20c1313d22148a58e97c75a36bdb

Merge pull request #173 from geut/dpaez/release-1.0.11 Release: 1.0.11

view details

push time in 2 months

PR merged geut/permanent-seeder

Release: 1.0.11

new release candidate.

It contains some tweaks and fixes for building the dashboard and commenting the pr (publish action)

+17 -13

0 comment

8 changed files

dpaez

pr closed time in 2 months

PR opened geut/permanent-seeder

Release: 1.0.11

new release candidate.

It contains some tweaks and fixes for building the dashboard and commenting the pr (publish action)

+17 -13

0 comment

8 changed files

pr created time in 2 months

create barnchgeut/permanent-seeder

branch : dpaez/release-1.0.11

created branch time in 2 months

delete branch geut/permanent-seeder

delete branch : dpaez/fix-dashboard-build-resolve

delete time in 2 months

push eventgeut/permanent-seeder

Diego Paez

commit sha b6a9d01e8a1bee7d6de5b52efcede4af1e1435de

Fix: add missing env vars

view details

Diego

commit sha fd2aaf4177aa95606464ab43fd3a197a2414e4ce

Merge pull request #172 from geut/dpaez/fix-dashboard-build-resolve Fix: add missing env vars

view details

push time in 2 months

PR merged geut/permanent-seeder

Fix: add missing env vars dashboard actions

related to react dashboard build

+2 -0

0 comment

1 changed file

dpaez

pr closed time in 2 months

PR opened geut/permanent-seeder

Fix: add missing env vars dashboard actions

related to react dashboard build

+2 -0

0 comment

1 changed file

pr created time in 2 months

create barnchgeut/permanent-seeder

branch : dpaez/fix-dashboard-build-resolve

created branch time in 2 months

delete branch geut/permanent-seeder

delete branch : dpaez/fix-build-pr-comment

delete time in 2 months

push eventgeut/permanent-seeder

Diego Paez

commit sha 4cd68c4066fff6bd4457d3d99c11998313b910cd

Update: using context.issue.number to get pr number

view details

Diego Paez

commit sha e87dcb3bed9592996abbff00e093e586f47bb784

Update: bump github actions

view details

Diego

commit sha ae2af3d183643d29aca3e9ca46a51ea2c943f3cb

Merge pull request #171 from geut/dpaez/fix-build-pr-comment Update: using context.issue.number to get pr number

view details

push time in 2 months

PR merged geut/permanent-seeder

Update: using context.issue.number to get pr number

related to publish action

+2 -2

0 comment

1 changed file

dpaez

pr closed time in 2 months

push eventgeut/permanent-seeder

Diego Paez

commit sha e87dcb3bed9592996abbff00e093e586f47bb784

Update: bump github actions

view details

push time in 2 months

PR opened geut/permanent-seeder

Update: using context.issue.number to get pr number

related to publish action

+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchgeut/permanent-seeder

branch : dpaez/fix-build-pr-comment

created branch time in 2 months

push eventgeut/permanent-seeder

Diego Paez

commit sha 6eccc45fd67a745691a08cc8725e49a84fc2158d

Update: version bump

view details

Diego Paez

commit sha 92541a1c02f83ff8a11a6562b6dfa65db8be59fa

Update: changelog

view details

Diego

commit sha 798a4692a80d72316050b95e2b6b65bcfbdee94f

Merge pull request #170 from geut/dpaez/release-1.0.10 Release: 1.0.10

view details

push time in 2 months

PR merged geut/permanent-seeder

Release: 1.0.10 dashboard services

This PR is a new release candidate.

This PR brings:

  • API versioning. The API is versioned and the available endpoints are documented.
  • :new: files stats and info endpoints
  • :new: files stats and info endpoints per checkout (version)
  • :new: file download endpoint.
+18 -14

0 comment

8 changed files

dpaez

pr closed time in 2 months

PR opened geut/permanent-seeder

Release: 1.0.10 dashboard services

This PR is a new release candidate.

This PR brings:

  • API versioning. The API is versioned and the available endpoints are documented.
  • :new: files stats and info endpoints
  • :new: files stats and info endpoints per checkout (version)
  • :new: file download endpoint.
+18 -14

0 comment

8 changed files

pr created time in 2 months