Skip to content
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

Jarrod display player region #221

Closed
wants to merge 352 commits into from
Closed

Conversation

JarrodBlanton
Copy link
Collaborator

@JarrodBlanton JarrodBlanton commented Jan 30, 2018

  1. Displays the player's region underneath their tag.

  2. Admin functionality now allows admins to see other regions as read-only. If the admin is a super admin, they are allowed to select them. Added some additional css styling to make read-only look different.

Cooke, Brandon (bc719c) and others added 30 commits July 9, 2016 17:55
- Changed pull of entrantScore to get method for error handling.
- Refactored extra match details pull
* Query player list locally for player dropdown feature.
Don't hammer the server with pointless requests.

* pull all players from server so searchbar can search all players

* sort player name matches by quality of match
* ignore OOR players

* this commit should fix the region stuff

* fixed rankings for merge
…nt. Added functions for submitting respective forms.
…eckbox regions. Refactored js variables into one postParams variable.
@BrandonCookeDev
Copy link
Collaborator

changes here start at 12f4659

@jiangtyd
Copy link
Collaborator

can you make the base branch something less far away? o.o

@BrandonCookeDev
Copy link
Collaborator

I think we'd need to rebase, which I'm not super duper familiar with.
I don't think it will be an issue after these PRs.

@BrandonCookeDev
Copy link
Collaborator

I'll see what I can do tho

@jiangtyd
Copy link
Collaborator

rebasing is easy! ish

@BrandonCookeDev
Copy link
Collaborator

I know you taught me a command once, it was like

git rebase -i HEAD~X

where X is the number of commits back you want your base to start... iirc

@BrandonCookeDev BrandonCookeDev changed the base branch from master to brandon-adminconsole-usersgui January 30, 2018 01:48
@BrandonCookeDev BrandonCookeDev changed the base branch from brandon-adminconsole-usersgui to master January 30, 2018 01:48
@jiangtyd
Copy link
Collaborator

well, you can do that to edit your commit history, roughly

I'm just really confused how this branch is based on such an old commit; shouldn't people have checked out master and developed on top of it?

@jiangtyd
Copy link
Collaborator

jiangtyd commented Jan 30, 2018

oh this is a 2016 branch LOL

imo you should just create a new branch off master, and cherry-pick the commits you want onto it

... wait is it? i'm so confused

@BrandonCookeDev
Copy link
Collaborator

Well #219 did the same thing, I think that one is because I started that branch a long time ago then merged master into it. Idk, because I made #215 recently and this did not happen.

@BrandonCookeDev
Copy link
Collaborator

BrandonCookeDev commented Jan 30, 2018

I tried creating a new branch and then rebasing a commit range 12f4659 - 16eb03e to it but that did not work. I looked at a PR for it and it had the same list of extra commits.

After some reading, I've been trying to run something like this on another branch and I'm not getting much luck:

git cherry-pick 12f4659^..16eb03e

Thoughts?

@jiangtyd
Copy link
Collaborator

I feel like this should work? I'm not sure what commits you want exactly

@BrandonCookeDev
Copy link
Collaborator

That range in the cherry pick statement is the range that comprises the changes this or should reflect

Maybe I'm doing something wrong? I should just be able to run this from a totally new branch off master right?

@JarrodBlanton
Copy link
Collaborator Author

Closed bad PR. New PR at #224

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants