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

add feature:icon and enhancement labels automatically #1411

Conversation

Snailedlt
Copy link
Collaborator

Double check these details before you open a PR

  • PR does not match another non-stale PR currently opened

Features

add and labels to pull_request_template.md, so that the labels are added automatically when users copy the link

This PR closes #1399

Notes

I think this needs to be merged to master before it takes effect

…so that the labels are added automatically when users copy the link
@Snailedlt Snailedlt added enhancement devops Use this label for devops related enhancements labels Oct 2, 2022
@Snailedlt Snailedlt requested a review from Panquesito7 October 9, 2022 02:04
@Snailedlt Snailedlt added the hacktoberfest-accepted Accepted to be counted towards Hacktoberfest label Oct 31, 2022
Copy link
Contributor

@lunatic-fox lunatic-fox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved! ✔

Unfortunately yes, as you said, it'll need to be merged to master before it takes effect.

I've made a test and the template works only with default branches. Then, on the test, I've changed develop as the default branch and it worked. 🤔

@Snailedlt
Copy link
Collaborator Author

@lunatic-fox What do you mean by the template works only with default branches.?

@lunatic-fox
Copy link
Contributor

@lunatic-fox What do you mean by the template works only with default branches.?

Whoops, I mean it in singular: "default branch".

Take a look at main branch, is labeled with default. So the template will be based on info from main.
If default label is on develop, for instance, the template will be based on the info from develop.
It's the "Switch default branch" action. However, I made it just for test in a separated repo.

@Snailedlt
Copy link
Collaborator Author

aha! I didn't know that :( What a bummer! Well, not much we can do about it though I guess :/

Well, maybe we can consider making develop the default branch instead I guess? That will also make the repo look more active to outside contributors, since develop is updated much more often than master.

Just have to look at what the other consequences of changing the default branch would be. We can make a discussion about it if you also think it should be considered :)

@lunatic-fox
Copy link
Contributor

Nah, that's ok! I also discovered it now, because I was testing. 🙂

I got the same idea of using develop as the default branch, for the same reasons, but I think better take a look at the consequences even before open a discussion.

I'll bookmark this PR in my notifications. 📑

@Snailedlt
Copy link
Collaborator Author

Hmm, weird. It works on non-default branches for me.

See this example: https://github.com/devicons/devicon/compare/develop...Snailedlt:devicon:dup/check_if_pr_base_is_develop_on_icon_prs?quick_pull=1&template=new_icon.md&labels=feature:icon
image

Could you please double check if it works for you @lunatic-fox ?

@lunatic-fox
Copy link
Contributor

Hi @Snailedlt!

Yeah it'll work this way on any branch, but the issue that we're talking about before was related to when someone create a pull request the placeholder comment will be based on master branch, so it will not have the &labels=feature:icon suffix, even if this current PR is merged to develop branch.

To be clear, when this PR is merged to develop it'll not affect the placeholder link when we create a PR, but when a new version is released and eventually merged to main it will show the proper placeholder link.

How it is

How it should be

@Snailedlt
Copy link
Collaborator Author

@lunatic-fox Ahh yes, so then it's as I initially expected. Then there should be no issue merging it to develop now right? Also means that we don't need to change the default branch to master imo :)

@lunatic-fox
Copy link
Contributor

Yes, it's fine to merge to develop.

What I didn't test yet, and will not have much time to do now, was about the consequences to turning develop into the default branch, so the best by now it's leave the way it is, in my opinion. And merge your pull request to develop. Maybe we can work more on that idea in the future.

@Snailedlt
Copy link
Collaborator Author

Maybe we can work more on that idea in the future.

Definitely!

Yes, it's fine to merge to develop.

I'll merge then 👍

@Snailedlt Snailedlt merged commit e4b1ec4 into devicons:develop Jan 9, 2023
@Snailedlt Snailedlt mentioned this pull request Feb 5, 2024
GCHQDeveloper926 pushed a commit to GCHQDeveloper926/devicon that referenced this pull request Dec 20, 2024
…so that the labels are added automatically when users copy the link (devicons#1411)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops Use this label for devops related enhancements enhancement hacktoberfest-accepted Accepted to be counted towards Hacktoberfest
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants