Here's the Weekly Digest for alejandro5042/azdo-userscripts:

ISSUES

Last week, no issues were created.

PULL REQUESTS

Last week, 1 pull request was created, updated or merged.

MERGED PULL REQUEST

Last week, 1 pull request was merged.
💜 #19 Code of the Day button should appear on newly created comments, by m-akinc

COMMITS

Last week there was 1 commit.
🛠️ Code of the Day button should appear on newly created comments (#19) When you initiate a new comment (or thread), the element with class 'vc-discussion-comments' is created, but the 'vc-discussion-comment-toolbar' isn't created until after you commit your text. by m-akinc

CONTRIBUTORS

Last week there was 1 contributor.
👤 m-akinc

STARGAZERS

Last week there were no stargazers.

RELEASES

Last week there was 1 release.
🚀 v2.26.2

That's all for last week, please 👀 Watch and ⭐ Star the repository alejandro5042/azdo-userscripts to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

It appears that this userscript is not working in Firefox anymore. I know it did work.

Below are screenshots of the same page in Chrome (where it does work) and Firefox (where it does not work).

I cannot confirm if this is an Firefox, Tampermonkey or userscript error.

Screenshots

Screenshot Chrome:

Screenshot Firefox:

Logs

Can't find any errors in the developer console.

Context

• Extension Version: 2.51.0 (latest)
• Browser: Firefox 83.0 (64-bit)
• URL: dev.azure.com/account
• "New Repos pull request experience" disabled

Some PRs come in dynamically after I've run the dashboard enhancement. I need to keep looking for new PR rows and process them as they come in.

It would be nice to not have the button for deleted files. I will work on having the diff tool better handle new files so it just opens them with LV instead of trying to diff them.

Never know where the "Auto-complete" tag is going to show up. Sometimes it sticks to the right of the title. Sometimes it is in with all the other tags.

Screenshots

Logs

N/A

Context

• Extension Version: 2.45.1
• Browser: Unknown
• URL: Unknown

I've noticed this week that the current version (2.51.0) of the AzDO userscript many of us have installed now hides scrollbars in Edge (87.0.664.75 64-bit). This seems to happen on AzDO pages that have horizontal content wider than the browser window, like build logs or PR diffs.

I've only started seeing this problem since early-mid January - probably broken by the latest Edge version - but I know the script has specific functionality around trying to show scrollbars and that seems to be failing.

Note, I don't think horizontal scrollbars are appearing either but the vertical ones were what I really noticed.

Logs

If applicable, add any relevant messages or errors you see in the browser's JavaScript console.

Context

• Extension Version: 2.51.0
• Browser: Edge 87.0.664.75 64-bit (Windows 10 64-bit v1903)
• URL: [non-public - contact me directly if you need it]

When rapidly switching tabs, such as from Declined to Reviewed in the Assigned to me section of dev.azure.com/ni/_pulls, there is a race condition where annotations that were supposed to go to a PR of one tab end up on the PR of another tab. See this GIF, which shows the days old and/or Last Reviewer annotations ending up on the Reviewed PR depending upon how quickly I switch away from the Declined tab after it starts loading:

Alejandro B. added the ability to see who is 'Following' a work item.

I am hoping for an OR of both of the below such that all possible notifications are visible:

• 'Following'
• Rules such as below is set such that a person would get a notification:
  • 'A work item I created is changed'
  • 'A work item assigned to me is changed'

This would allow me to tell, through all means, which persons will be notified. For example, our team mostly uses the rules and not 'Follow'. So, it's difficult for me to tell who will get a notification just through 'Follow' listing. Thanks.

Here's the Teams thread which caused the script to me created (and my original request):
https://teams.microsoft.com/l/message/19:[email protected]/1600440116221?tenantId=87ba1f9a-44cd-43a6-b008-6fdb45a5204e&groupId=6ed8db9a-c7ab-481b-8e9b-ee5608937d8a&parentMessageId=1600440116221&teamName=ASW%20%26%20DSW&channelName=General&createdTime=1600440116221

When in Firefox's dark theme mode, the dialog box for Tampermonkey » More Awesome Azure DevOps (userscript) » Configure PR Status Location has white text on a white background, which effectively renders your radio button selection invisible unless you drag-select over the text to view it. See screenshot

Logs

N/A

Context

• Userscript Manager: Tampermonkey
• Extension Version: 3.0.1
• Browser: Firefox 88.0 (64-bit)
• URL: ni.visualstudio.com

We need to find a better color.

Context

• Extension Version: 2.53

Here's the Weekly Digest for alejandro5042/azdo-userscripts:

ISSUES

Last week, no issues were created.

PULL REQUESTS

Last week, no pull requests were created, updated or merged.

COMMITS

Last week there were no commits.

CONTRIBUTORS

Last week there were no contributors.

STARGAZERS

Last week there were no stargazers.

RELEASES

Last week there were no releases.

That's all for last week, please 👀 Watch and ⭐ Star the repository alejandro5042/azdo-userscripts to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

When I last tested it, the userscript did not work in ViolentMonkey. VM is an open source userscript manager. TamperMonkey used to be open source, but now isn't.

This issue captures making the userscript work in VM, and updating all the docs to promote the use of VM over TM. However, we should continue to support TM.

Context

• Extension Version: 2.49
• Browser: Chrome

NI has an official JS style guide that is in-work, based on Airbnb. We should upgrade to use it:

https://github.com/ni/javascript-styleguide/

Here's the Weekly Digest for alejandro5042/azdo-userscripts:

ISSUES

Last week 1 issue was created.
It is still open.

OPEN ISSUES

💚 #37 Bump eslint-plugin-react from 7.16.0 to 7.17.0, by dependabot-preview[bot]

NOISY ISSUE

🔈 #37 Bump eslint-plugin-react from 7.16.0 to 7.17.0, by dependabot-preview[bot]
It received 1 comments.

PULL REQUESTS

Last week, 1 pull request was created, updated or merged.

UPDATED PULL REQUEST

Last week, 1 pull request was updated.
💛 #37 Bump eslint-plugin-react from 7.16.0 to 7.17.0, by dependabot-preview[bot]

COMMITS

Last week there were no commits.

CONTRIBUTORS

Last week there were no contributors.

STARGAZERS

Last week there were no stargazers.

RELEASES

Last week there were no releases.

That's all for last week, please 👀 Watch and ⭐ Star the repository alejandro5042/azdo-userscripts to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

When a build is configured to expire after a period of time, the build result icon on the PR landing page should update to say that the build for that PR is broken. Currently, it looks up the result of the build, so the landing page shows that the build has passed whereas it actually needs to be run again.

Maybe we can report an expired build separately from a failed build? I'm thinking of an icon like " ✔⌚ " (bonus points for finding a single unicode character that combines these two) for builds that passed but have expired.

If a build has failed then it doesn't matter if it has also expired, since the crucial information is that the build failed.

When enabling this preview feature:

The UI is totally different and the dashboard sorting doesn't work (but doesn't break the page either).

Context

• Extension Version: All
• Browser: All
• URL: All

When using the period shortcut to go from an Azure DevOps Repo to vscode.dev it doesn't always open the right branch. I'd guess it's because Azure DevOps doesn't always have the branch name in the URL. I think Azure DevOps only adds the branch name to the URL when you change it in the UI or use a link that contains the branch. Otherwise it always opens to the last branch you were viewing but doesn't add that to the URL even if it's not the main or default branch for the repo.

I have this in a dev branch. I should just push it out next time I clean out my dev branches in the userscript repo on superawesome.

Here's the Weekly Digest for alejandro5042/azdo-userscripts:

ISSUES

Last week, no issues were created.

PULL REQUESTS

Last week, no pull requests were created, updated or merged.

COMMITS

Last week there were no commits.

CONTRIBUTORS

Last week there were no contributors.

STARGAZERS

Last week there were no stargazers.

RELEASES

Last week there were no releases.

That's all for last week, please 👀 Watch and ⭐ Star the repository alejandro5042/azdo-userscripts to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

Fix the individual PR pages under the new experience.

https://devblogs.microsoft.com/devops/introducing-the-new-pull-request-experience-for-azure-repos/ ?

Context

• Extension Version: 2.41.4
• Browser: All
• URL: All

Here's the Weekly Digest for alejandro5042/azdo-userscripts:

ISSUES

Last week 1 issue was created.
It is still open.

OPEN ISSUES

💚 #12 Add Code of the Day PR flagging, by m-akinc

PULL REQUESTS

Last week, 1 pull request was created, updated or merged.

UPDATED PULL REQUEST

Last week, 1 pull request was updated.
💛 #12 Add Code of the Day PR flagging, by m-akinc

COMMITS

Last week there were no commits.

CONTRIBUTORS

Last week there were no contributors.

STARGAZERS

Last week there were no stargazers.

RELEASES

Last week there were no releases.

That's all for last week, please 👀 Watch and ⭐ Star the repository alejandro5042/azdo-userscripts to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

When I am reviewing a pull request or viewing code in a web browser, I would like to be able to click on the string "AB#123456" in a code comment and open the corresponding Azure Boards work item.

Will this userscript be ready for the New Pull Request Experience for Azure Repos: https://devblogs.microsoft.com/devops/introducing-the-new-pull-request-experience-for-azure-repos/ ?

Context

• Extension Version: 2.41.4
• Browser: Firefox 75.0 (64-bit)
• URL: dev.azure.com/account

Is your feature request related to a problem? Please describe.

I'm looking at a PR consisting of a Markdown file (.md). When viewed as plaintext, many text blocks are wider than my window. This leads to a bunch of frustrating horizontal scrolling. It's not technically a problem with the Markdown as when rendered the text will be wrapped to the window width.

Describe the solution you'd like

It would be nice if I could enable word wrap and have these long lines wrap at the width of the window.

Describe alternatives you've considered

I suppose I could copy the diff into a text editor like Microsoft Notepad and use its word wrap feature. 🤮

Additional context

NI: you can message me in Teams if you'd like to see the PR I'm referencing for yourself.

Is your feature request related to a problem? Please describe.

It would be useful to be able to hide the list of reviews that you have created in AzureDevOps.
For example at the moment I have ~12 PR's created by me, in various stages of the development cycle. I don't really care to see these PR's as I'm doing code reviews for my collaborators. It's just wasted real-estate.

Describe the solution you'd like

The functionality already seems to exist to add a collapsable list to the assigned reviews. Potentially this some functionality could be hooked up to work on the "Create by me" reviews.

Describe alternatives you've considered

I don't believe there is an alternative available besides just living without the feature.

Additional context

N/A

Here's the Weekly Digest for alejandro5042/azdo-userscripts:

ISSUES

Last week 2 issues were created.
Of these, 2 issues have been closed and 0 issues are still open.

CLOSED ISSUES

❤️ #15 Sort prs by added date, by m-akinc
❤️ #14 Fix bug in "notable activity" logic, by m-akinc

NOISY ISSUE

🔈 #14 Fix bug in "notable activity" logic, by m-akinc
It received 1 comments.

PULL REQUESTS

Last week, 3 pull requests were created, updated or merged.

MERGED PULL REQUEST

Last week, 3 pull requests were merged.
💜 #15 Sort prs by added date, by m-akinc
💜 #14 Fix bug in "notable activity" logic, by m-akinc
💜 #12 Add Code of the Day PR flagging, by m-akinc

COMMITS

Last week there were 4 commits.
🛠️ [Sort prs by added date (#15) Before separating PR dashboard rows into different buckets (e.g. Drafts, Approved, etc), set their relative order based on when the user was (most recently) added to the review.

The most direct way I know of to get that information is by looking for the comment thread that announces when a reviewer is added to the PR. We were already querying the threads for PRs that the user had approved (in order to check for "notable activity"), but now we have to do this for all PRs the user is on. That will result in a performance hit, but it should be acceptable.](f0206e3) by m-akinc
🛠️ [Fix bug in "notable activity" logic (#14) I stumbled on this bug by examination, not by noticing incorrect behavior. However, the symptoms would be:

Any thread in the PR with enough words or comments in it could trigger the "notable activity" categorization -- even those threads that happened before the user approved the PR.
The "notable activity" categorization never triggers based on other reviewers giving rejected/waiting votes.](d539622) by m-akinc
🛠️ Rev version for COD features by alejandro5042
🛠️ [Add Code of the Day PR flagging (#12) A user wanted to be able to flag a certain PR thread so that he could later write a "Code of the Day" blog post about it. To avoid embarrassing anyone, it has to be implemented in a way that it's not obvious when someone's PR/thread has been flagged.

I added a button next to the "like comment" button that toggles whether the thread is flagged (individual comments are not flagged). When a thread is flagged the button icon and the tooltip changes. You only see the flag statuses that you have set. If other people flag a thread, you will not see it, and you can toggle your own flagged state for that thread independently.

The flagged thread states for a particular PR are persisted in a hidden property (NI.CodeOfTheDay) on that PR. These states will be fetched via a script. One limitation of this persistence approach is that completing a PR effectively "freezes" all COD flagging on it. You can't modify the properties on a completed PR.](79210b7) by m-akinc

CONTRIBUTORS

Last week there were 2 contributors.
👤 m-akinc
👤 alejandro5042

STARGAZERS

Last week there was 1 stargazer.
⭐ ccifra
You are the star! 🌟

RELEASES

Last week there were 3 releases.
🚀 v2.26.0
🚀 v2.25.0
🚀 v2.24.0

That's all for last week, please 👀 Watch and ⭐ Star the repository alejandro5042/azdo-userscripts to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

Is your feature request related to a problem? Please describe.

We want a frictionless way for users of the wiki to provide feedback to authors when a page is helpful or unhelpful.

Describe the solution you'd like

1. "thumbs up" and "thumbs down" buttons added to every page. We may add various "down" buttons for different complaints (content missing, content incorrect, etc). We may also add an optional free text field to describe the feedback in more detail.
2. votes are recorded by adding/modifying a wiki attachment.
3. stats about recent votes are displayed on each page alongside existing page view stats. The stats are also available if we want to write tools to harvest and display them in other formats (spreadsheet, dashboard, etc).

Describe alternatives you've considered

1. sending users to a separate page to provide feedback (for example a short survey). This adds a tiny bit more friction than the proposed approach so we're worried it would result in less feedback being submitted.
2. storing feedback in other ways besides a wiki attachment.
   • we could store votes as a markdown comment within the content of each page. That seems like it would get in the way when users are editing the page contents.
   • it would be nice to use a properties API like we use for pull request code of the day ideas but I don't see a similar API for wiki pages

• we could send the votes to a separate server but that would make the user script more tied to NI's infrastructure and would require managing that server

Additional context

There is a similar idea on the AzDO developer community but it doesn't look very popular.

This is similar to the feedback feature on MSDN

Overview

Recently, a feature was added to allow editing of files from PRs. The "Edit" button for a file is visible when selecting a folder/section under the files navigation pane. It would be nice if there was a way to edit a file when a single file was selected in the files navigation pane.

Is your feature request related to a problem? Please describe.

I recently had a PR where I was migrating code. The PR contained more than a 1000 files. I wanted to make a quick edit a file that was towards the bottom and at the root level. Using the current "Edit" button was not realistic since I would need to select the outermost folder and then scroll through >1000 files to find the one I wanted edit.

Describe the solution you'd like

I want the ability to select a single file in the files navigation pane and have some way to edit that file. I think there are a lot of different ways the edit operation could be made available that would work for me.

Describe alternatives you've considered

None

Additional context

None

Is your feature request related to a problem? Please describe.

PRH plans on adding the whole domain to every FPGA review (as an AzDo team, now that Mert has done that). This is to give visibility to changes being made, without blocking the review on a lot of people.

We have mostly gotten rid of vertical code owners in our niconfig in favor of horizontal code owners (feature vs chapter). This is going to cause my PR view to become very noisy and I want to make sure I'm seeing changes to files I care about, even if I'm not an niconfig reviewer.

Describe the solution you'd like

I'd like a way to make custom details elements based on the AzDo query API.

Describe alternatives you've considered

Because that is so ambitious I'd also be OK with a details elements that queried the files for a certain regex. Some PRs might show up in multiple details elements but thats OK.

Additional context

Here's the Weekly Digest for alejandro5042/azdo-userscripts:

ISSUES

Last week 2 issues were created.
Of these, 2 issues have been closed and 0 issues are still open.

CLOSED ISSUES

❤️ #6 Expanding on SUPPORT.md and adding welcome bot support, by alejandro5042
❤️ #5 Improvements to the PR diff, by alejandro5042

PULL REQUESTS

Last week, 2 pull requests were created, updated or merged.

MERGED PULL REQUEST

Last week, 2 pull requests were merged.
💜 #6 Expanding on SUPPORT.md and adding welcome bot support, by alejandro5042
💜 #5 Improvements to the PR diff, by alejandro5042

COMMITS

Last week there were 14 commits.
🛠️ Fix CSS id by alejandro5042
🛠️ Restore side-by-side diffs to full width by alejandro5042
🛠️ Update README.md by alejandro5042
🛠️ Update README.md by alejandro5042
🛠️ Improvements to the PR diff (#5) Improvements to the PR diff by alejandro5042
🛠️ Merge branch 'master' into fix-pr-diff by alejandro5042
🛠️ Added links to docs by alejandro5042
🛠️ Reverting LICENSE.md rename by alejandro5042
🛠️ Rename LICENSE to LICENSE.md by alejandro5042
🛠️ Update CONTRIBUTING.md by alejandro5042
🛠️ Expanding on SUPPORT.md and adding welcome bot support (#6) Expanding on SUPPORT.md and adding welcome bot support by alejandro5042
🛠️ Expanding on SUPPORT.md and adding welcome bot support by alejandro5042
🛠️ Updated README explaining new features by alejandro5042
🛠️ Improvements to the PR diff - Make the horizontal scrollbar always visible - Make the file name always visible, even if the user scrolled down the page by alejandro5042

CONTRIBUTORS

Last week there was 1 contributor.
👤 alejandro5042

STARGAZERS

Last week there were no stargazers.

RELEASES

Last week there were 3 releases.
🚀 v2.20.2
🚀 v2.20.1
🚀 v2.20.0

That's all for last week, please 👀 Watch and ⭐ Star the repository alejandro5042/azdo-userscripts to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

Is your feature request related to a problem? Please describe.

It would be nice to easily spot it when someone, say, marks a Comment as won't fix without any comments

Describe the solution you'd like

Describe alternatives you've considered

N/A

Additional context

N/A

When a user clicks the "Follow" button for a work-item, the list of "following" should be updated as well.

Workadound:

• Click Follow
• Refresh page

Due to the changes to click 'Show more items' in the New and Closed columns, even if I have these columns closed, they are forced back expanded to click that button every time the page refreshes.

I have a couple approaches to resolve this up for review, but neither were ideal, so I'm filing this issue.

Revert: #112

Try to add a toggle to disable this functionality: xhuff@5e9e48e

When I have Declined a review, it's a little misleading to see a red Last Reviewer annotation. I'm not considered in the list of reviewers blocking a PR, so I'm not really the last reviewer. Perhaps this annotation should be left off when Declined.

It's less clear to me how to handle mere Optional reviewers. They're not blocking, but they're still people considered in the list of reviewers. I think my preference is to exclude all Optional reviewers, whether Declined or not, as the red Last Reviewer annotation seems intended to prevent PRs from being blocked.

On the latest version of the script, it collapses-by-default changes that you aren't the Owner/Alternate/Export for. However, as the author of the PR, I'd like to see all the changes by default.

I think by-design it shouldn't collapse these, as I wish to review all of my own changes :)

DevOps already shows you in how many files the PR changes code. I would love to extend that feature with total lines added, deleted and the delta of those 2 (added-delted).
This helps to estimate how long you might need to review that PR, so you can plan ahead more precisely.

What do you think about that @alejandro5042

Is your feature request related to a problem? Please describe.

I am involved in a workflow where I frequently find myself bypassing owners and this idea will make it slightly faster.

Describe the solution you'd like

I would like there to be a default reason when bypassing owners, similar to the reviewboard user script.

Show how many files we own:

Requested by Adam Arnesen.

When you have a PR targeted at something other than master, the dashboard shows a good build check when no builds have actually been run. Might be better to omit the build glyph in this case.

Screenshots

None.

Logs

None.

Context

• Extension Version: v2.45.1
• Browser: Unknown
• URL: Unknown

Noticed someone who wanted to emphasize their note so they bolded the word note. Unfortunately that made the script not recognize it as a note. This keyword identification should ignore formatting markup and leading whitespace.

Context

• Extension Version: 2.49.0

@humberto-garza Have you thought about extending the button to also work on /commit/ pages? It seems like it would be quite useful when looking at VI changes in main.

The extension randomly stopped working, all functionality seems to be busted.
Logs below...

Logs

Uncaught (in promise) TypeError: Cannot convert undefined or null to object
at hasOwnProperty ()
at getReviewerAddedOrResetTimestamp (userscript.html?id=f6a99515-d69c-42b4-952d-0c095dfee583:1143)
at HTMLDivElement.eval (userscript.html?id=f6a99515-d69c-42b4-952d-0c095dfee583:1045)

Context

• Extension Version: 2.26.0
• Browser: Google Chrome 77.0.3865.90
• URL: N/A

Educate new users that there's a way to preview Markdown files. This is useful for manager-types that don't do PRs often but may need to review a spec in AzDO occasionally, and aren't fully aware of these AzDO features.

The recent feature:
PR: Show who else follows work item #110

Is only showing the current user in the list of "following".
I did a test with another developer to both follow an item and make sure it was happening on his side too. And it did.

Screenshots

N/A

Logs

N/A

Context

• Extension Version: 2.49.1
• Browser: Windows Chrome / Version 85.0.4183.121 (Official Build) (64-bit)
• URL: (dev.azure.com/account or account.visualstudio.com)

When a PR has new updates (like comments you haven't viewed yet), that PR ends up not grayed out in the dashboard. If they didn't reset my status, then it is not time for me to look again.

Context

• Extension Version: 2.49.0
• Browser: Chrome 85.0.4183.121

Draw a line when the PR went to owners (NI only).

Besides owners, also consider a line between state changes:

• Draft
• Published
• Abandoned

Here's the Weekly Digest for alejandro5042/azdo-userscripts:

ISSUES

Last week 4 issues were created.
Of these, 2 issues have been closed and 2 issues are still open.

OPEN ISSUES

💚 #20 Feature: Add the ability to hide/collapse the "Created by me" reviews., by bgianfo
💚 #19 Code of the Day button should appear on newly created comments, by m-akinc

CLOSED ISSUES

❤️ #18 Avoid calling hasOwnProperty on a null value, by m-akinc
❤️ #17 Extension Errors out with: Cannot convert undefined or null to object at hasOwnProperty, by bgianfo

NOISY ISSUE

🔈 #17 Extension Errors out with: Cannot convert undefined or null to object at hasOwnProperty, by bgianfo
It received 3 comments.

PULL REQUESTS

Last week, 2 pull requests were created, updated or merged.

UPDATED PULL REQUEST

Last week, 1 pull request was updated.
💛 #19 Code of the Day button should appear on newly created comments, by m-akinc

MERGED PULL REQUEST

Last week, 1 pull request was merged.
💜 #18 Avoid calling hasOwnProperty on a null value, by m-akinc

COMMITS

Last week there was 1 commit.
🛠️ Avoid calling hasOwnProperty on a null value (#18) This fixes issue #17. Don't assume the thread has properties. by m-akinc

CONTRIBUTORS

Last week there was 1 contributor.
👤 m-akinc

STARGAZERS

Last week there were no stargazers.

RELEASES

Last week there was 1 release.
🚀 v2.26.1

That's all for last week, please 👀 Watch and ⭐ Star the repository alejandro5042/azdo-userscripts to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

Here's the Weekly Digest for alejandro5042/azdo-userscripts:

ISSUES

Last week 1 issue was created.
It is still open.

OPEN ISSUES

💚 #35 IGNORE - Test PR, by alejandro5042

NOISY ISSUE

🔈 #35 IGNORE - Test PR, by alejandro5042
It received 1 comments.

PULL REQUESTS

Last week, 1 pull request was created, updated or merged.

UPDATED PULL REQUEST

Last week, 1 pull request was updated.
💛 #35 IGNORE - Test PR, by alejandro5042

COMMITS

Last week there was 1 commit.
🛠️ Fix multiple auto-collapse button bug Make the auto-collapse button not reappear when switching updates. by alejandro5042

CONTRIBUTORS

Last week there was 1 contributor.
👤 alejandro5042

STARGAZERS

Last week there were no stargazers.

RELEASES

Last week there was 1 release.
🚀 v2.30.1

That's all for last week, please 👀 Watch and ⭐ Star the repository alejandro5042/azdo-userscripts to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆