I like the idea for sure. Could issues and PRs be created in GitSteem directly and then duplicated over on GitHub via the API? Could synchronization there happen as well, so any updates to existing items are also reflected on Github? I think it would be much more useful if there was no double entry and everything could be done in GitSteem directly without having to first create PRs or issues in Github.
You are viewing a single comment's thread from:
You should be able to use the APIs to replicate the data. Then again, with the data existing on the blockchain, why even post it on github? :)
I was kind of thinking the same thing. Maybe post the first few lines and then an awesome ASCII nag screen of sorts that says something like:
------------------------------------------------------ To view and contribute to this conversation, join GitSteem. Get paid for your open source efforts. ------------------------------------------------------If someone really wanted to make it happen, I wonder if even various aspects of the github data (diffs, etc) could be displayed natively in GitSteem.
Interesting idea, for sure.
Pipe dream could be to stop using github all together and launch a new blockchain where the git info was stored on-chain -
VCS Coingo!Yeah, I was thinking about that also. It's all just text files under the hood, right?
Between the two of you this could be built over the weekend!
I'll play the role of jr dev.
[insert easy button here]
Hah! It'd be a fun project, that's for sure. Not so sure about the idea of doing it in a weekend... but still :)
You can for both.
Pull request: https://developer.github.com/v3/pulls/#create-a-pull-request
Issue: https://developer.github.com/v3/issues/#create-an-issue
I believe you would need to update the scope of the oath to include
public_repothat would allow read/write privileges for that user's public repos.