I have lots of old and useless notifications when I mark them done they go to "done" section (obviously) but I couldn't find a way to remove them completely. How can I remove these old notifications from my life?
There does not seem a way to manually clear out the Done section.
The documentation simply mentions:
Notifications marked as Done are saved for 5 months.
So they are cleared out eventually, but not immediately.
Related
Current update schedule is too frequent to me. The editor pops out update reminder every 3-4 days.
I don't need so frequent update reminder. It's annoying to me. I am only interested in major release.
So how to get less update notification? (Every month or quarter would be preferred).
(Because of the annoyance, currently, I just ignore all update notifications. I understand it could be risky and it's not a good practice)
Current version number looks like: XX.YY.ZZ. How to only subscribe XX.YY update (ignore ZZ update)? Thanks
Thanks
You can switch to manual updates in the settings (Ctrl + ,).
This will disable the notification, and checking for updates manually will only be 2 clicks away:
I accidentally created an issue when setting up my first board. I have no need to delete the Issue - it has nothing attached to it. But I just want to keep my board clean.
Is there a way to actually delete this issue?
A little bit late to the party, but according to ZenHub docs
It is not possible to delete a Release once it has been created.
Closing a Release will remove it from your Board and filters. This
release will only be visible to users scrolling through the list of
closed releases in the Release report tab.
I have pushed two changes to AOSP, same topic and they have been sitting with "Needs Code-Review Label" for 3 days now (weekend included).
I know I can assign reviewers manually, but I wouldn't know who to add. I've read around on how to submit a patch but have not found if reviewers are automatically notified and the change will be processed whenever it should or if there is something else on my side I have to do.
You just need to wait or you could, if was the case, add specific reviewers for your change. It's seens that 3 days (weekend included) aren't time enought for the review.
Did the "outdated diff functionality" get removed or are we just using comments wrong now?
Whenever a updated a review comment I no longer get the "outdated diff functionality". This makes it extremely hard to keep track of what was updated when working with a team.
Cheers.
Edit
Received an e-mail from github that explained the functionality is no longer active and that they are working on bringing it back again.
Received an e-mail from github that explained the functionality is no longer active and that they are working on bringing it back again.
It has been restored.
A couple of years ago, I uploaded a module to CPAN that probably isn't or hasn't been of use to anyone. The problem it solves is simple, it doesn't solve it well, and the code embarrasses me.
How can I remove it?
Log in to your PAUSE account and there is a menu item to delete your files. The files will be scheduled to be deleted 3 days hence (giving you a change to change your mind), and maybe another day after that for the change to be propagated to all the CPAN mirrors.
By design, this will not delete your files from the BackPAN.
2021 update Sometime around 2015, PAUSE changed the way they manage meta-data by not tracking the meta-data not derived from the release itself. These options have disappeared from the PAUSE interface years ago (although I wasn't able to pin it down from looking at the commit messages).
It's not like most of that ever really did anything. Marking something "can be deleted" didn't mean it would be deleted.
Besides deleting all the files, which you can still do, if you need extra help, you can write to the admins.
You can delete files from CPAN by marking them for deletion in PAUSE. This only removes them from the master repository that PAUSE maintains. It does not send out signals to the universe to delete all copies ever created.
If you've registered it in the module list, you can set its lifecycle to "Can be deleted from database" by editing the module metadata. This does not immediately remove it, but it can be removed the next time PAUSE does a database cleanup.
This doesn't make the code disappear from the world. It will not be on the main CPAN server, but it can still show up on mirror sites and in BackPAN.
But, don't despair about bad code. Everyone has embarrassing code somewhere in CPAN. Even if the code is incomplete or buggy, it might be a good starting point for other people with a related problem.
I'd suggest you leave it on CPAN but change the primary maintainer to ADOPTME, the PAUSE ID we use for modules who have lost their maintainers. If you have it registered in the module list, you can also mark it as "abandoned" under Support Level by editing the module metadata.