Closed BeepBot99 closed 8 months ago
Also remove high priority and low priority, those can go in the project too.
I will do it all.
@Mesure73L Do I have permission to start?
OK I started.
What? I never said you could start.
Please undo whatever you did.
Not everything is Twelve of Code, therefore not in the project. The labels also allow you to see the status easily while in the issues page. There is a use for those labels, and they should not be deleted. The labels also allow you to filter by priority, so you can see everything that is high priority and not assigned, for example.
Please undo everything you did related to this issue, and read #62.
Not everything is Twelve of Code, therefore not in the project.
Yes, I know, I realized that after I did it.
The labels also allow you to see the status easily while in the issues page.
It can be configured so project statuses do too.
The labels also allow you to filter by priority, so you can see everything that is high priority and not assigned, for example.
You can create a priority field too. In addition, having two separate fields for priority and status can help you sort it even better.
Please undo everything you did related to this issue, and read #62.
I will not do that (yet), read this first.
Tell me which one you choose, and I will do it.
@Mesure73L Answer this whenever you are ready to, I will not do anything until then. Please do not do anything related to the project will me showing you how first. It is not completely set up yet.
Basically, we can't use labels for 12oC. It is just a matter of what you want to do with the rest of the website.
Please do not do anything related to the project will me showing you how first?
Basically, we can't use labels for 12oC. It is just a matter of what you want to do with the rest of the website.
Why not?
@BeepBot99
What do you mean without you showing me how first?
We cannot use labels because you cannot use them with projects (unless you are willing to pay 10 dollars a month.)
@Mesure73L
What do you mean without you showing me how first?
Read it again. (its your message lol)
We cannot use labels because you cannot use them with projects (unless you are willing to pay 10 dollars a month.)
WHat else would I get with it?
Please send me the link to that subscription.
https://github.com/pricing You would need to get team. You would have to pay 8 dollars a month (two people) because I am not paying for it because I don't care and it doesn't work unless everyone has it.
I wouldn't recommend it though.
It would be a lot harder to set up. I can add the statuses back, they just wouldn't be used for 12oC.
Why can't we use labels with 12oC? How does it know it's status related
Do you want a short explanation or a long one? A long one will take me a few minutes to type.
Do you want a short explanation or a long one? A long one will take me a few minutes to type.
Long one
Oh you weren't lying about that the longer one would take more time to type
ok this is a lot more than a few minutes
@BeepBot99 can you please give the explanation?
I'm at school you know, be patient please /srs. I'll do it now.
be patient please /srs
take your own advice bro
So, the problem is basically that they are two seperate things. It is possible to have both at the same time, there is no problem with that. However, they will not by synced. They will be two completely seperate systems. If there is only one system in place, not only will it be significantly easier to manage, but it will also be easier to see insights into it. You can pay to sync the two systems.
Re-add the labels, let's just not sync the two systems.
OK. But, the statuses will ALWAYS have top priority NO MATTER WHAT.
I will do it later. Only status and priority labels were removed. You can do it now if you want.
OK. But, the statuses will ALWAYS have top priority NO MATTER WHAT.
dang i didn't know you would be this upset
I will do it later. Only status and priority labels were removed. You can do it now if you want.
you were the one who removed it, you are the one who adds it back
@Mesure73L Can we call tonight to talk about this?
https://github.com/marketplace/actions/project-beta-automations I'm going to try this in a testing repository.
Merging this into #51.
Unmerging this.
I'm going to start doing this, but I might not finish.
@Mesure73L It is possible and easy to make it so that when the labels change, the item's status in the project changes. However, that is only one way. Currently, there is no GitHub Actions trigger to detect when an item changes status in a project. The solution to that would be to check every issue's status every hour, and then update the labels only every hour. Is that fine with you. In addition, what would happen if, for instance, it has two different contradicting labels? It cannot have two different statuses.
We probably shouldn't run it every hour though, because we only get 2,000 Actions minutes per month.
I think this problem is actually fixed, by creating the other project. We do not need the labels anymore,
Okay, good. I had thought that this wasn't completed for two reasons:
However, it doesn't matter anymore, because it is fixed now!
What problem were you having?
We should not have status-related labels, such as
ready to merge
andin progress
. Because, there are already statuses in the project.What solution would you like?
Remove all the status related labels
What alternatives have you considered?
Make it a lot harder to automate
What are some pros and cons of doing this?
Pros
Cons
What page is this for?
No response
What steps need to be done?