-
Notifications
You must be signed in to change notification settings - Fork 101
Mixed improvements on server and client #27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@@ -32,7 +32,7 @@ var svg_background_color_online = '#0288D1', | |||
|
|||
|
|||
|
|||
var socket = io(document.location.hostname); | |||
var socket = io(document.location.host); |
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.
Thanks for the PR!
Could you please fix the merge conflict here.
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.
On it!
The GitHub API doesn't actually return `action = merged' when a PR is merged; it just sets `pull_request.merged = true'. From the Description field for the Action key: https://developer.github.com/v3/activity/events/types/#pullrequestevent
With this commit each event has a proper link directing to the actual event, except PushEvents which direct to the repo since there isn't any available link to the commits.
That was quick! 😄 |
I was waiting for it 😊 On another topic, these binaries are huge, it'd be better putting them in another place: maybe using github LFS or just putting them as a release which doesn't involve any additional installation. In any case that would involve rewriting history to delete them out of the repository, because it has become super-slow to fetch and push due to the extra 80MB. It would probably involve telling people that you rebased master, but since it's 8 days ago it shouldn't have much impact and the benefit is clear. |
Just one catch here. Now push events are redirecting to |
Maybe that's fine, I'm not sure what users prefer. |
Oh sorry I thought I fixed it. It seems I didn't double check it and the API docs are wrong, there doesn't seem to be any { id: '4745514621',
type: 'PushEvent',
actor:
{ id: 7099784,
login: 'docbacardi',
display_login: 'docbacardi',
gravatar_id: '',
url: 'https://api.github.com/users/docbacardi',
avatar_url: 'https://avatars.githubusercontent.com/u/7099784?' },
repo:
{ id: 70711456,
name: 'muhkuh-sys/org.muhkuh.lua-jonchki',
url: 'https://api.github.com/repos/muhkuh-sys/org.muhkuh.lua-jonchki' },
payload:
{ push_id: 1360737728,
size: 5,
distinct_size: 5,
ref: 'refs/heads/master',
head: '13ab152ce613758121339bd3a5b0ff1bea5d9790',
before: '35d914f64b3d61b65d66859a3e4687b339bd4428',
commits: [ [Object], [Object], [Object], [Object], [Object] ] },
public: true,
created_at: '2016-10-21T07:41:23Z',
org:
{ id: 7113795,
login: 'muhkuh-sys',
gravatar_id: '',
url: 'https://api.github.com/orgs/muhkuh-sys',
avatar_url: 'https://avatars.githubusercontent.com/u/7113795?' } } It should be easy to change just manually concatenating the repo_name, as it was before in the client side: diff --git a/server/index.js b/server/index.js
index caa879e..36b0774 100755
--- a/server/index.js
+++ b/server/index.js
@@ -117,7 +117,7 @@ function stripData(data){
'payload_size': data.payload.size,
'message': data.payload.commits[0].message,
'created': data.created_at,
- 'url': data.repo.url
+ 'url': 'https://github.com/' + data.repo.name
});
pushEventCounter++;
} |
Thanks! I'll do it. |
Make sure to remove the binaries, it will be a huge source of pain in the future, that happened to me as well. |
Did you mean to remove the binary files and rebase to the commit prior to the commit having binary files? |
No, that won't work. You have to make an interactive rebase to the commit prior to the one having binary files. You can use
It seems you'll only have to edit 864d3ea (Add binaries for macOS and Linux) and afaa324 (Move bin to static). If you're unfamiliar with rebase interactive let me know, but there should be a helpful explanation of how to use it once you run the Let me know if I need to explain further! Oh, and at some point you'll have to also change the URLs from index.html but that can be done afterwards. |
I've found a way to do it programatically better. Make sure you're on the most updated master and you have your zip files backed up somewhere else:
This reduces significantly the size of the git repository:
Afterwards, you have to make a force push |
Mixed improvements on server and client
Mixed improvements on server and client
Mixed improvements on server and client
This PR contains the following improvements:
cross-env
dependency so thatnpm start
works.merged
when appropriate: as is now, closed and merged PRs have both anaction = closed
. See the description of the action field in the PullRequestEvent documentation.Tested locally.