labels on pull request are not visible

[reshamsai150]

when the issue is assigned some labels are assigned like levels, GSSOC but when I completed the pull request labels for that issue were not visible on the pull request

[Lelin07]

@reshamsai150
Regarding the issue you mentioned, it seems like the labels assigned to the issue aren't appearing on the pull request after completion. This could be due to a few reasons. One possibility is that the labels were assigned to the issue itself rather than the pull request. When you create a pull request, GitHub doesn't automatically carry over the labels from the associated issue. You'll need to manually add them to the pull request.

To do this, you can navigate to the pull request page, click on the "Labels" dropdown menu (if it's open to do so), and select the appropriate labels that were assigned to the issue. This should ensure that the labels are visible on the pull request for better organization and tracking.

If you encounter any further issues or have any more questions, feel free to ask! Also, once your question is resolved, could you please mark it as answered? This helps keep the forum organized and lets others know that a solution has been found.

[aryansharma220]

The labels you mentioned (levels, GSSOC) are likely project management labels used by the maintainers to organize and categorize issues within the repository. These labels are typically not automatically transferred or applied to pull requests when you submit one.

Pull requests and issues are separate entities in a repository, even though they may be related. The labels assigned to an issue are meant to provide context and metadata for that specific issue. When you create a pull request to address that issue, the pull request itself does not inherit those labels by default.

However, there are a few reasons why the labels might not be visible on your pull request:

1. Manual label assignment: In some projects, maintainers manually assign relevant labels to pull requests based on the changes or the associated issue. This process is often done during the review stage.

2. Automated labeling: Some repositories have automated workflows or bots that can add labels to pull requests based on certain conditions or triggers, such as the presence of specific keywords in the pull request title or description, or if the pull request is linked to a labeled issue.

3. Repository settings: The repository settings may be configured to not display labels from issues on pull requests, or vice versa.

If you believe that the labels from the associated issue should be visible on your pull request, you can try the following:

1. Mention the issue in the pull request description: Clearly reference the issue number in your pull request description. This can help maintainers and automated workflows identify the connection between the pull request and the labeled issue.

2. Request label assignment: In the pull request description or comments, politely ask the maintainers to assign the relevant labels to your pull request for better organization and tracking.

3. Check the project documentation: Some projects have specific guidelines or processes for labeling pull requests. Refer to the project's documentation or contributing guidelines for more information.

4. Reach out to maintainers: If the labeling process is unclear or you believe there might be a configuration issue, respectfully reach out to the project maintainers and inquire about the labeling process for pull requests.

Ultimately, the decision to assign labels to pull requests lies with the project maintainers, but open communication and following the project's guidelines can help ensure that your contribution is properly organized and tracked.

[aswinikalyan30]

Please ask the project admins/mentors to assign the PR to you and add relevant labels. You can add a comment on the PR regarding the same

[Ojas-Arora]

When labels assigned to an issue are not visible on a related pull request, it tells that there is a disconnect between the issue and the pull request, or that the labels were not transferred automatically.
@reshamsai150

[vidheeagrawal]

@reshamsai150 hey watch the mentor's video once again. https://www.youtube.com/watch?v=Y9PYaPZgikg
You will get to know that its not necessary that every time labels will be there, you can add label by yourself also.

[nishant05gaurav]

There may be a few reasons why the characters you saw in the original might not appear in your download request:

Label Visibility: It is possible that the labels you see in the article (such as "Levels" or "GSSOC") are not set to appear in pull requests. This is a policy controlled by the store owner and can be customized.

Incorrect labeling: It is possible that the labels were mistakenly applied to the original problem instead of the pull request. Labeling is often used to categorize problems, while a pull request usually has its own set of labels used to track the development process (e.g., "Needs Review," "Ready to Merge").

Limited permissions: In some cases, users with limited permissions may not be able to see all characters that have been used for an issue or pull request.

Here’s how to approach this situation.

Ask the shop cleaning staff: Contact the shop cleaners and ask about missing labels. They can clarify whether pull requests should get scored and help you understand the default workflow.

Double-check the lines: Check the pull request yourself. Some platforms allow labels to be added directly to the pull request. If they are missing, see if there is a way to add the appropriate labels ("Levels" or "GSSOC") to your pull request.

Leave a comment: If you are unsure or the lines are completely missing, leave a comment about the withdrawal request describing the missing line and why it might be relevant. This helps bring it closer to the critics.

[nileshsn]

@reshamsai150

Ah, got it. If the labels assigned to the issue aren't showing up on your PR, it might be a good idea to ensure that your PR references the issue number correctly in its description or title. Sometimes, the labels don't automatically transfer, but mentioning the issue number usually helps maintain context for reviewers and evaluators.