This adds an accessor for the zoom_name to the contributor profile.
Doing this also removes general support for preserviing the contributor
accounts array as this was buggy and caused accounts to be added
multiple times.
This adds an accessor for the zoom_name to the contributor profile.
Doing this also removes general support for preserviing the contributor
accounts array as this was buggy and caused accounts to be added
multiple times.
sadly I have issues with my setup since the weekend after I did a system upgrade and I don't get aragon cli and some native dependencies installed. so far I failed to fix it, thus this is untested PR so far.
sadly I have issues with my setup since the weekend after I did a system upgrade and I don't get aragon cli and some native dependencies installed. so far I failed to fix it, thus this is untested PR so far.
sadly I have issues with my setup since the weekend after I did a system upgrade
You don't have a way of rolling back your system to a working state? If you still use Arch, I can highly recommend creating Timeshift snapshots before upgrades, so you don't get into this situation again.
> sadly I have issues with my setup since the weekend after I did a system upgrade
You don't have a way of rolling back your system to a working state? If you still use Arch, I can highly recommend creating Timeshift snapshots before upgrades, so you don't get into this situation again.
See e.g. https://itsfoss.com/backup-restore-linux-timeshift/
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This adds an accessor for the zoom_name to the contributor profile.
Doing this also removes general support for preserviing the contributor
accounts array as this was buggy and caused accounts to be added
multiple times.
sadly I have issues with my setup since the weekend after I did a system upgrade and I don't get aragon cli and some native dependencies installed. so far I failed to fix it, thus this is untested PR so far.
There are some Travis errors you can look at (and linting should work locally without Aragon CLI, too).
You don't have a way of rolling back your system to a working state? If you still use Arch, I can highly recommend creating Timeshift snapshots before upgrades, so you don't get into this situation again.
See e.g. https://itsfoss.com/backup-restore-linux-timeshift/
Tested successfully with my WIP branch of kredits-web. 👍
I changed the serialized property name to better reflect the actual data.
yeah, thanks for the hint. I am using timeshift, but it is some node.js and npm only issue I did not want to rollback.