Syncing labels and status field about mesure.x10.mx HOT 43 CLOSED

Also remove high priority and low priority, those can go in the project too.

from mesure.x10.mx.

I will do it all.

from mesure.x10.mx.

@Mesure73L Do I have permission to start?

from mesure.x10.mx.

OK I started.

from mesure.x10.mx.

What? I never said you could start.

from mesure.x10.mx.

Please undo whatever you did.

from mesure.x10.mx.

The reason why this isn't accepted:

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.

from mesure.x10.mx.

Comments on what you just said

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.

Options from here

1. This is my top choice. I know you will probably not do it, but I am just mentioning it to say that it is still an option. It is to create a new repository for 12oC. Then, everything will be seperate.
2. Create a project for the main website, in addition to the one for 12oC. Then, both projects can have their own stuff, and there will be no need for labels.
3. Keep it as it is and add the labels back, but use the labels only for non-12oC stuff. If we do this, then there will also need to be seperate issue templates for 12oC.

Tell me which one you choose, and I will do it.

from mesure.x10.mx.

@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.

from mesure.x10.mx.

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.

from mesure.x10.mx.

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?

from mesure.x10.mx.

@BeepBot99

from mesure.x10.mx.

What do you mean without you showing me how first?

from mesure.x10.mx.

We cannot use labels because you cannot use them with projects (unless you are willing to pay 10 dollars a month.)

from mesure.x10.mx.

@Mesure73L

from mesure.x10.mx.

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?

from mesure.x10.mx.

Please send me the link to that subscription.

from mesure.x10.mx.

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.

from mesure.x10.mx.

I wouldn't recommend it though.

from mesure.x10.mx.

It would be a lot harder to set up.
I can add the statuses back, they just wouldn't be used for 12oC.

from mesure.x10.mx.

Why can't we use labels with 12oC? How does it know it's status related

from mesure.x10.mx.

Do you want a short explanation or a long one? A long one will take me a few minutes to type.

from mesure.x10.mx.

Do you want a short explanation or a long one? A long one will take me a few minutes to type.

Long one

from mesure.x10.mx.

Oh you weren't lying about that the longer one would take more time to type

from mesure.x10.mx.

ok this is a lot more than a few minutes

from mesure.x10.mx.

@BeepBot99 can you please give the explanation?

from mesure.x10.mx.

I'm at school you know, be patient please /srs.
I'll do it now.

from mesure.x10.mx.

be patient please /srs

take your own advice bro

from mesure.x10.mx.

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.

from mesure.x10.mx.

Re-add the labels, let's just not sync the two systems.

from mesure.x10.mx.

OK. But, the statuses will ALWAYS have top priority NO MATTER WHAT.

from mesure.x10.mx.

I will do it later. Only status and priority labels were removed. You can do it now if you want.

from mesure.x10.mx.

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

from mesure.x10.mx.

@Mesure73L Can we call tonight to talk about this?

from mesure.x10.mx.

https://github.com/marketplace/actions/project-beta-automations
I'm going to try this in a testing repository.

from mesure.x10.mx.

Merging this into #51.

from mesure.x10.mx.

Unmerging this.

from mesure.x10.mx.

I'm going to start doing this, but I might not finish.

from mesure.x10.mx.

Hi, currently waiting on this.

from mesure.x10.mx.

@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.

from mesure.x10.mx.

We probably shouldn't run it every hour though, because we only get 2,000 Actions minutes per month.

from mesure.x10.mx.

I think this problem is actually fixed, by creating the other project. We do not need the labels anymore,

from mesure.x10.mx.

Okay, good. I had thought that this wasn't completed for two reasons:

1. Originally, I had suggested having two different projects, and you had said no.
2. Once we had two seperate projects, you said I still needed to attempt this when I could finish.

However, it doesn't matter anymore, because it is fixed now!

from mesure.x10.mx.