Fix #3062: Label added to AdministratorControlsActivity.

[jkugsiya]

Explanation

Fixes #3062 : Added label to AdministratorControlsActivity.

Checklist

• The PR title starts with "Fix #bugnum: ", followed by a short, clear summary of the changes. (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
• The PR explanation includes the words "Fixes #bugnum: ..." (or "Fixes part of #bugnum" if the PR only partially fixes an issue).
• The PR follows the style guide.
• The PR does not contain any unnecessary auto-generated code from Android Studio.
• The PR is made from a branch that's not called "develop".
• The PR is made from a branch that is up-to-date with "develop".
• The PR's branch is based on "develop" and not on any other branch.
• The PR is assigned to an appropriate reviewer in both the Assignees and the Reviewers sections.

Screenshot of successful test:

[anandwana001]

Follow - https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section

[jkugsiya]

Follow - https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section

I unassigned myself and requested a review.

[anandwana001]

@jkugsiya Could you confirm, if you have access to the Assignee section?

[jkugsiya]

@jkugsiya Could you confirm, if you have access to the Assignee section?

No, I don't have access to that!

[rt4914]

@jkugsiya Thanks.

[rt4914]

@jkugsiya One nit change.

Also, this PR contains changes related to formatting of the AndroidManifest and strings file which I think is correct change otherwise other contributors will face this same issue. But I will defer to @BenHenning about this.

[rt4914]

LGTM, thanks.

[jkugsiya]

I've updated the fork's branch and that is reflecting the changes and showing that it is up-to-date. https://github.com/jkugsiya/oppia-android/tree/A11y-AdministratorControlsActivity

But I don't know why the same is not reflecting in the PR.

Can someone help me resolve this problem?

[anandwana001]

@jkugsiya As Fetch Upstream is something GitHub has released on the repository directly, but this will not push to your PR. This is only updating your branch on the fork, not pushed into the PR.

[jkugsiya]

@jkugsiya As Fetch Upstream is something GitHub has released on the repository directly, but this will not push to your PR. This is only updating your branch on the fork, not pushed into the PR.

How can I push to the PR then? As all the changes are done and there's nothing to commit more.

[anandwana001]

You need to check if your local PR branch is synced with the repository or not. If not then git pull and update the PR, and then you need to push to this PR.

[jkugsiya]

You need to check if your local PR branch is synced with the repository or not. If not then git pull and update the PR, and then you need to push to this PR.

Already done the specified. Still no luck! Shows Everything up-to-date

[jkugsiya]

You need to check if your local PR branch is synced with the repository or not. If not then git pull and update the PR, and then you need to push to this PR.

Already done the specified. Still no luck! Shows Everything up-to-date

It automatically appeared now, without doing anything. It could have been an issue with GitHub. Thanks @anandwana001 !!

[BenHenning]

Thanks @jkugsiya. This LGTM.

[BenHenning]

@anandwana001 I think you're requesting changes which is blocking this PR--PTAL.

[anandwana001]

LGTM