-
Notifications
You must be signed in to change notification settings - Fork 110
Conversation
I personally suggest deleting |
agree with @nonsense about |
@skylenet why do we need to commit the build files into the repo? they should be generated on a build hook and published somewhere. i don't see any reason why they should be here. only sources |
wow. good catch! |
a438f1b
to
2f233c9
Compare
2f233c9
to
107de96
Compare
@acud I've deleted the build dir and also created a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for this, did you also already check how the deployment works? Will the automatic deployment still work after we merge?
@nonsense there was something which looked like a refresh button, but it actually means "re-request review", that is then what happened and a review has been re-requested to you :) sorry for that. |
https://swarm-guide.readthedocs.io/en/latest/ is now using the source from I've also moved recent issues from the For now I've archived the |
* master: network/newstream: new stream! protocol base implementation (#1500) swarm: fix bzz_info.port when using dynamic port allocation (#1537) cmd/swarm: make bzzaccount flag optional and add bzzkeyhex flag (#1531) cmd/swarm: remove separate function to parse env vars (#1536) network/bitvector: Multibit set/unset + string rep (#1530) swarm: 0.4.3 unstable (#1526) travis: also build on release tags (#1527) swarm: release v0.4.2 (#1496) network: bump bzz stream hive (#1522) docker: update ca-certificates file (#1525) Add swarm guide to /docs (#1513) network/simulation: Add ExecAdapter capability to swarm simulations (#1503)
Imported from ethersphere/swarm-guide (
master@1f8d30f
)Todo after merging:
swarm-guide
project, change Repository URL tohttps://github.com/ethersphere/swarm