Uh thanks! GitHub rate limits are annoying when cloning big projects.

(Just jocking :D)

......also, that lint issue would be resolved, doing this

On the paper we could:

To the CentOS 7 user surfing to this patch: please kill your server with as much violence as possible, since your server is a security hole with software around.

AOSC OS you said? Learned a new thing. So, approved.

Does it still work if there are not compilation flags in CXXFLAGS? I assume yes, but I don't know anything about makefiles lol

Check if you like the bonus point

Oh God yes! Thanks!!

In T15100#5480, avivey wrote:

@MBinder_WMF - how much of this will be solved if we just add a tooltip to the [ X | Y / Z ] header?

Uhm while visiting the page D25491 click things, I was able to crash production Phorge with

The funny part about T16104 is that the "Point limit", yes, it applies to points (when they are enabled), but the same amount applies to the count of tasks when points are disabled. So it affects WIP bars.

P.S. the email contained in this image is in the public domain, from my friend Fabio, from the public repository Libre BusTO. https://gitpull.it/source/libre-busto/repository/master/

P.S. the email contained in this image is in the public domain, from my friend Fabio, from the public repository Libre BusTO. https://gitpull.it/source/libre-busto/repository/master/

@deric congratulations for this double-approval and feel free to:

move #accadf to #3498db as suggested by 20after4 and Iniquity

I agree with @20after4 and @Iniquity since the proposed color #3498db was really too much bright and it was difficult to distinguish a link from a normal text. Their proposed #accadf seems good.

P.S. please help in reviewing the colors in D25491 - I absolutely don't know which color would be nice

In T15056#21859, @danielyepezgarces wrote:

I guess this is also disappointing for "True Kanban" users (?)

Oh God. So, if I understand correctly, the whole thing is probably just here:

Thanks @Iniquity 👍 added in the task description!

Premising that I trust the stakeholders here when they report that Phorge does silly thing on Kanban, for their workflows;

Wow, that utility is utilized and uteful 🧐

In D25569#28533, @mainframe98 wrote:

Is throwing an error in the JavaScript really necessary? Regardless, this works as advertised.

How the hell did you review this in less than a minute? 😄

Note that Phorge has phutil_string_cast() that does the (string) cast, probably useful somewhere, especially from points where alien objects could arrive from the ski (e.g. database entities).

Patch ready for testing in my production as usual lol D25569

OK added last Test Plan about nonsense stuff like http://phorge.localhost/P1#LMIAAAO - I've concluded the test plan ideas. Seems to work.

improve JavaScript DOC to mention '@throws' and when

Commanding. So others must approve.

git rebase master to get the new mailkey fancy thing

Please just @aklapper click on all comments of mine and say "done" since I can't lol (T15332)

It works. Waiting for more +1 since I should not self-approve lol.

fuck with celerity

• implement 'L' prefixed lines to make W3C happy
• implement support for 'L1-999' intervals so we don't need '$' there
• implement startup support, so at startup the '#L123' works

Uh, I've found some time to have #L123-124 working too! 🎉 wait for it

Can I help to adopt L123?

@aklapper Can you upload 5dec8bf28557f078d1987c4e8cfb53d08310f522.gitpatch.real ?

I've followed again the test plan (but arc land) and everything works, especially "arc anoid". Arc anoid keeps all my damn infrastructure up and running 24/7 so this patch can be approved.

Thanks (about that unit test, it never worked, see T16098)

I'm a simple person, I see PHPDoc, I approve PHPDoc. We want more. Thanks

Sorry markup

Sorry² tuples

Sorry tuples

Yeah, I like Setup Warnings. The EXPLAIN SELECT * FROM table could be a good trick to have an efficient estimation of the table size, without actually causing a full table scan (e.g. COUNT(*) is bad)

P.S. file a task for that broken unit test on your computer :D :D ideally finding if with git bisect you discover a regression

«There's a known problem with 8.2 though» Ouch I don't remember what was this about 🤔 uhm

Unrelated troubleshooting but what about this?

What about landing this?