Open tpmccauley opened 5 years ago
@JG-QuarkNet do you see this issue in the tab? or anywhere?
The issue showed up on the Issues tab of the QuarkNet GitHub page ( https://github.com/QuarkNet-HEP/cima-wzh/). I still don't see anything on yours (https://github.com/tpmccauley/cima-wzh).
On Wed, Jul 10, 2019 at 11:37 AM Tom McCauley notifications@github.com wrote:
@JG-QuarkNet https://github.com/JG-QuarkNet do you see this issue in the tab? or anywhere?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/QuarkNet-HEP/cima-wzh/issues/2?email_source=notifications&email_token=AD7LDOQIED3BMFTFDZNV7J3P6X63JA5CNFSM4H7QN5RKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZT3T6A#issuecomment-510114296, or mute the thread https://github.com/notifications/unsubscribe-auth/AD7LDOSHTBLKR7FX7OJNMU3P6X63JANCNFSM4H7QN5RA .
I just made my QuarkNet-HEP membership public
I understand now. Issues only appear in the "master" repo, i.e. this one. Not on forks. Are you able to assign this issue?
Looks like it.
So we still have the problem of how I open issues on your Docker branch, because the issues I want to open concern the README, which isn't present on the originating repo.
In that case you can comment on the pull request. Alternatively merge the pull request and then open an issue.
On Wed, 10 Jul 2019, 18:03 JG-QuarkNet, notifications@github.com wrote:
Looks like it.
So we still have the problem of how I open issues on your Docker branch, because the issues I want to open concern the README, which isn't present on the originating repo.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/QuarkNet-HEP/cima-wzh/issues/2?email_source=notifications&email_token=AADZG56VCWDWFFR7765DKEDP6YI7TA5CNFSM4H7QN5RKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZUDO4Q#issuecomment-510146418, or mute the thread https://github.com/notifications/unsubscribe-auth/AADZG52P4DECDZKUZ7BTXMTP6YI7TANCNFSM4H7QN5RA .
chart.js must be upgraded to resolve this. #4
On the X axis the bin labels should mark the borders of the bins not the center. This is more intuitive.