Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Activity for sau226
Type | On... | Excerpt | Status | Date |
---|---|---|---|---|
Comment | Post #287893 |
We've since created GitHub issue #1115 to track this request (https://github.com/codidact/qpixel/issues/1115). A PR was also submitted to fix this issue.
As the PR has been merged, and the issue closed, we've updated the tag on this post to status-planned pending code deployment.
Thanks for rep... (more) |
— | 9 months ago |
Comment | Post #287893 |
From a technical standpoint, this behavior occurs because we create a "post history" event for the "initial revision" of every post, and that table pulls post history events.
We could conceivably add an additional filter to the relevant queries, which would hide the initial revision altogether as ... (more) |
— | about 1 year ago |
Comment | Post #277057 |
Sorry for not picking up this request earlier. I've opened https://github.com/codidact/qpixel/issues/812 to get this request assessed and potentially implemented.
In the meantime, I'll tag this post as status-deferred. This is probably a nitpick that would be nice for us to fix, but ultimately is ... (more) |
— | almost 2 years ago |
Comment | Post #286192 |
We currently have 3 things that need to occur before this goes live:
** A dev needs to release the design system NPM package. The code is already sitting in the repo, but this step has not been taken yet
** A PR which bumps the design system NPM package (already created) will need to be merged ... (more) |
— | almost 2 years ago |
Comment | Post #286374 |
Re your comment above, see my reply below:
* I agree that unless we make a change that could be classified as "administrative" or "required by law/to be in compliance with law", a notice period would be useful for a change. Unfortunately we don't have that technology yet, so I offered the model clau... (more) |
— | almost 2 years ago |
Comment | Post #286332 |
Point 1: You don't "own" your account per se, you are using an external service, so you are granted a license to use that service. We are not as legally wordy as most services are, but most larger sites only grant you a revocable license to use their site. If the site revokes your license to use it, ... (more) |
— | almost 2 years ago |
Comment | Post #285470 |
We got upgraded to GitHub Team plan a while back, so I guess we can configure autolinking for our main repo.
See https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources for configurat... (more) |
— | about 2 years ago |
Comment | Post #285449 |
We moved the dashboard link to the header with commit c10970d, however for various reasons this only was deployed a day or two ago.
Sorry for the wait! (more) |
— | about 2 years ago |
Comment | Post #286060 |
We've fixed this in commit c4e4367, which was deployed along with other changes today. (more) |
— | about 2 years ago |
Comment | Post #284726 |
We don’t have any intentions of using Facebook or Reddit for product support - things become complicated (e.g. how do we verify who a user is etc.) and we just can’t justify doing so at this size and scope.
Whatever is on the contact form is guaranteed to be working and will allow for private matt... (more) |
— | over 2 years ago |
Comment | Post #283235 |
The changes are now deployed to production and these errors should no longer occur. (more) |
— | over 2 years ago |
Comment | Post #282165 |
The check that decides what text to render in that location was checking for an ability with internal name 'edit_post', while the actual ability is called 'edit_posts' (note the 's').
Fix submitted, should be merged in the near future and all will be well with the deploy after merge (more) |
— | almost 3 years ago |
Comment | Post #281882 |
@JohnDoea I've gone into the support ticketing system and updated the relevant template. Those emails should now include a copy of the text you submit with a ticket next time you file a ticket. Thanks for the report. (more) |
— | almost 3 years ago |
Comment | Post #281311 |
The issue with 500 flag errors has been resolved in code via commit 59dcb6b, however the fix will not be available on site until the next deploy (next time site version at bottom of page is changed). (more) |
— | about 3 years ago |
Comment | Post #281449 |
Have we considered changing the thresholds to be lower by default in the code, and then adding a setting that we can flip to bump them up, when the site is deemed to be "mature" and "active", thus requiring higher thresholds? (more) |
— | about 3 years ago |
Comment | Post #280086 |
Code fix filed as PR #378 (more) |
— | over 3 years ago |
Comment | Post #280116 |
Code fix has been filed via PR for suggested edit notifications. If there are any other notifications that are erroring like this, please name them in a comment here for the record. (more) |
— | over 3 years ago |
Comment | Post #279670 |
A code fix has been offered for this issue and is currently pending review (more) |
— | over 3 years ago |
Comment | Post #279669 |
A code fix has been offered for this issue and is currently pending review. For future reference, the help articles don't support markdown, only HTML. (more) |
— | over 3 years ago |
Comment | Post #278803 |
There's a known issue with the box not staying closed across page refreshes. A fix for that has been offered and will ensure that the box does stay closed. (more) |
— | over 3 years ago |
Comment | Post #278726 |
By way of example, I am mentioning Open Collective (https://opencollective.com), which is a reputable system for handling contributor payments (they are used by webpack and curl, just to name 2 examples), in case an interested staffer comes across this post looking for relevant systems. (more) |
— | over 3 years ago |