1import{_ as A}from"./CZZwVole.js";import{e as D,r as s,h as R,o as n,c as a,b as r,w as v,a as e,d as w,i as S,v as T,n as I,F as y,m as f,f as b,s as N,x as z,_ as F,t as c,p as u,A as W}from"./OlwiJrpn.js";import{B as m}from"./D388sAuY.js";import{m as L}from"./DGoZ2IfO.js";import"./DlAUqK2U.js";const q=[{name:"Custom Dashboard Layouts",image:"/changelog/custom-dashboard-layout.webp",tags:["New Feature","Improvement","Customization","Developer experience"],publicationDate:"Aug 1, 2025",content:`We're continuing our mission to make engineering metrics more relevant to your team. 2 3This update brings major flexibility to how your team sees and organizes engineering data, and brings new correlation insights to help drive more informed conversations. 4 5## ð New 6 7- **Custom dashboard layouts** 8 You can now choose which metrics appear on your main dashboard and rearrange their layout to match your team's priorities. 9 10- **Correlation charts** 11 We've added new charts to help you explore how **Batch Size** relates to other key metrics like **Cycle Time**, **WIP Time**, **Pickup Time**, **Review Time**, and **Merge Time**. These insights help identify bottlenecks and opportunities for improvement. 12 13## ð Improvements 14 15- **Developer View preview and customization** 16 Admins and Managers can now **preview** the _Developer View_, seeing exactly what a developer sees across tabs and metrics. Admins can also **configure** which metrics are shown in the _Developer View_, hiding sensitive data or highlighting specific metrics to guide team conversations. 17 18## ð¬ Feedback is welcome 19 20These changes are part of a broader effort to make Pullpo's metrics system more adaptive. If there's a metric you'd love to track or correlate, let us know ;) 21`},{name:"Higher Flexibility in Metrics Visualization",image:"/changelog/health_grades.webp",tags:["New Feature","Improvement","Customization"],publicationDate:"Jul 11, 2025",content:` 22We're currently focused on giving you more control over how your team views and organizes the engineering metrics that matter most to you. This first update in that direction introduces new options for defining how metrics are calculated and visualized. 23 24## ð New 25 26- **Multi-squad metrics** 27 28 Metrics can now be computed across any subset of squads, not just organization-wide or per individual squad. This is ideal for cross-squad initiatives and allows for more nuanced groupings. 29 30- **Chart resolution** 31 32 A new option in the "Advanced settings" dropdown (located next to the time range selector) lets you control the level of aggregation in your dashboard charts. How many sub-periods should the selected time range be divided into? 33 34- **Percentile-based metrics** 35 36 In that same dropdown, you can now choose to compute metrics base on either the average or a percentile (from P50 to P90). These advanced settings are stored in your session and applied as your defalt visualization preference. 37 38- **Dashboard header** 39 40 We've added a new summary section at the top of the Metrics dashboard, showing a quick overview of your team's **Velocity**, **Quality**, and **Developer Experience**. These are displayed as grades (A+, A, B, C) to give you a quick pulse of your team's health at a glance. 41 42## ð Improvements 43 44- **PR Analyzer performance** 45 46 We've significantly improved load times in the PR Analyzer tab, which is particularly noticeable for large teams segmenting data by applying multiple filters. 47 48- **PR reminders** 49 50 We continue to work with you to find edge cases and make PR reminders smarter, more accurate, and less noisy. 51 52## ð Sneak peek 53 54As your team grows, so does your need for nuanced insights and control over how metrics are displayed. Next up: even more customization options, bringing metric flexibility to where your team needs it most! ð 55 `},{name:"New Permissions System and Developer View",image:"/changelog/pullpo-dev-view.webp",tags:["New Feature","Improvement","Developer Experience","Security"],publicationDate:"June 15, 2025",content:` 56How do you give developers access to valuable team metrics without accidentally encouraging individual comparisons or _finger-pointing_? 57Promoting this healthy engineering culture is the core principle behind our new permissions system and _Developer View_. 58 59## ð New 60 61- **Role-Based Access Control** 62 63 We've completely revamped our permissions system to be more intuitive and secure. Instead of the previous READ_ALL, WRITE_ALL, and ADMIN permissions, we now have a role-based system with scope limitations: 64 65 | Role | Description | Scope | 66 |------|-------------|--------| 67 | Admin | Full access to all features and settings | Whole team | 68 | Manager | Access to metrics and settings | Whole team or subset of squads (customizable per-user) |
69 | Developer | Access to relevant* metrics | Whole team or subset of squads (customizable per-user) | 70 | Member | No access | | 71 72- **Developer View*** 73 74 A new way to explore Pullpo's insights dashboard, safely: 75 - **Read-only access** to the **Metrics**, **Surveys** and **Settings** tabs. Data is scoped to the team and subset of squads as defined in the user's permissions. 76 - Only **aggregated** data is shown. Sensitive details like specific PRs that miss obectives and individual feedback remain visible only to Managers. 77 - **Filtering by individual developers is disabled**, making it easy to analyze team patterns while preventing direct comparisons. 78 - Encourages **healthy team engagement** with metrics, promoting transparency while maintaining data security. 79 80This update reflects our commitment to making Pullpo more accessible to all team members while maintaining proper security controls and preventing misuse of metrics data. 81 82 `},{name:"Working Hours, AI Reviewer, and Conventional Comments Updates",image:"/changelog/working-hours.gif",tags:["New Feature","Improvement","Developer Experience","AI"],publicationDate:"May 30, 2025",content:` 83This update brings exciting new features to help teams work more efficiently and maintain better control over their notifications and reviews. 84 85## ð New 86 87- **Working Hours Configuration** 88 89 Teams can now set their working hours to ensure that reminders and alerts are only sent during appropriate times. This helps maintain work-life balance and prevents notification fatigue by respecting each team's schedule. 90 91- **[AI Reviewer with Custom Rules](https://pullpo.io/products/ai-reviewer)** 92 93 We're thrilled to announce the launch of our AI Reviewer feature! This powerful tool allows teams to: 94 - Create custom rules for code review 95 - Generate intelligent summaries of changes 96 - Maintain consistent review standards across the team 97 - Save time on routine review tasks 98 99## ð Improvements 100 101- **Conventional Comments GitLab Integration** 102 103 Our Conventional Comments extension now integrates seamlessly with GitLab, making it easier than ever to maintain consistent communication standards in your pull requests. 104 105 `},{name:"Supercharging PR-Channels: Conventional Comments, Enhanced Formatting & More!",image:"/changelog/cc-mrkdwn.png",tags:["New Feature","Improvement","Developer Experience","Tooling"],publicationDate:"May 9, 2025",content:` 106 This update is all about refining your Pull Request workflow and giving you more power and flexibility within Pullpo's tooling. 107 108 ## ð New 109 110 - **Conventional Comments browser extension (Chrome & Firefox)** 111 112 We've launched our **Conventional Comments browser extension**, available for both [Chrome](https://chromewebstore.google.com/detail/conventional-comments-git/gelgbjildgbbfgfgpibgcnolcipinmlp) and [Firefox](https://addons.mozilla.org/en-US/firefox/addon/conventional-comments-pullpo). It adds a toolbar to GitHub comment boxes, providing shortcuts for labels (like \`suggestion:\`, \`issue:\`, \`praise:\`) and decorators (e.g., \`(blocking)\`, \`(non-blocking)\`) to better convey intent and importance. 113 114 We've also made sure they render beautifully within your **PR-Channels** on Slack! 115 116 - **Pattern matching for Repository & Branch filters** 117 118 You can now use **pattern matching** when specifying repository or branch names to include or exclude in your metrics. For example, easily exclude all test branches by adding a rule like \`test/*\`. 119 120 ## ð Improvements 121 122 - **Prettier Slack message formatting from Git markdown** 123 124 We've revamped our parser to ensure that markdown and HTML-like syntax from your Git provider's messages are translated beautifully into Slack. Text style stays consistent, lists maintain their structure, \`<table>\` tags look like actual tables, and even attached images and \`<details>\` blocks are now formatted correctly. \\ 125 No more deciphering ugly bot messages! 126 127 - **AI-Analyzer: Now more flexible!** 128 129 Some teams prefer to use reminders and feedback requests without opening a dedicated channel for _every_ PR, but still want the AI summary on the Git provider's page. So we've **decoupled the AI-Analyzer from PR-Channels**. 130 131 ## ð Fixes 132 133 - Addressed an issue where reviewer updates in some specific sce
133narios prevented dynamic PR-Status messages from displaying certain real-time updates. 134 - Resolved a bug that caused unwanted notifications on closed or merged PR-Channels when an involved member was removed from the Git organization. 135 - Optimized a performance bottleneck in activity metrics when filtering by squad over large time periods with high activity. Reports are now **blazing fast**! 136 `},{name:"Jira Integration, GitHub Re-review Requests on PR channels, Docs Refresh, and a Sneak Peek!",image:"/changelog/focus.png",tags:["New Integration","New Feature","Objective Metrics","Improvement","Developer Experience"],publicationDate:"April 4, 2025",content:` 137This week brings a few exciting updates, including a brand new integration and a little something extra we think you'll find interesting. 138 139## ð New 140 141- **Jira Software integration** 142 143 Current and future customers with access to *Pullpo Insights* can now connect their Jira instance to Pullpo and unlock additional metrics. 144 145 The first metric we've implemented is **"Focus distribution"**. This provides a clear view of how many issues of each type (bug, feature, task, etc.) your team completed during a selected period and, crucially, how that distribution changed over time. Our goal with this metric is to help teams gain awareness of the resources allocated to client-impacting work versus maintenance and bug fixes. 146 147 We have more Jira metrics in the pipeline, but we'd love to hear from you. What other interesting metrics would you find valuable to extract from your Jira Software data? Let us know in our Slack community or by reaching out to us at [email protected]. 148 149- **GitHub re-review request notifications on PR channels** 150 151 Now, when someone **re-requests a review** from a reviewer on GitHub, that person will get tagged in the notification sent through the associated PR channel on Slack. 152 153 â ï¸ This functionality is currently limited to GitHub due to the lack of equivalent webhook support from GitLab for this specific event. 154 155## ð Improvements 156 157- **Documentation refresh** 158 159 We've been a bit quiet on the changelog front lately, and that's because we've been doing some maintenance and dedicating some time to **re-writing a significant portion of our documentation**, which had become a little outdated. 160 161## ð Sneak peek 162 163For those of you curious enough to explore our newly updated documentation, you might stumble upon a little something we've been secretly working on: a **Chrome extension for "Conventional Comments"**. 164 165We're putting the finishing touches on this extension, and we're excited to announce that it will be **Open Source**! Stay tuned for its release! 166 `},{name:"Customer Requests Week!",image:"/changelog/ai-summary.gif",tags:["New Feature","Improvement","Develeloper Feedback"],publicationDate:"February 21, 2025",content:` 167This Week at Pullpo: Customer Requests Week! 168 169This week was all about our customers at Pullpo. We've been working every day to implement improvements and new features based on customer requests. 170 171As a reminder, you can always share feedback or request new features in our Slack community or by reaching out to us at [email protected]. 172 173## ð Improvements 174 175- **PR AI Analyzer**: We've made significant improvements to our AI bot that summarizes PRs in Pullpo. Now, in addition to providing a natural language summary of the PR, it also offers suggestions with specific code line references. Unlike other tools, Pullpo doesn't require write access to your code, ensuring your data remains secure. 176- **PR Description**: Synchronized in PR Slack Channels: This was an easy but important update. You can now edit PR descriptions, and they will automatically update in the associated PR channel. 177 178## ð Fixes 179- **Feature access in different plans**: Embarrassingly, in very specific cases, Pullpo wasn't properly restricting access to Pullpo Insights for users paying only for the Tooling plan. This issue is now fixed. 180 181 `},{name:"Improving DevEx Surveys",image:"/changelog/feb-14-2025.png",tags:["New Feature","Improvement","Develeloper Feedback"],publicationDate:"February 14, 2025",content:` 182 183Last week, we introduced the new *DevEx Surveys*, and since then, we've conducted several to assess their effectiveness. 184Two standout features our clients loved were **automatic DM reminders** and the ability to **pause and resume responses** at a more convenient time while preserving progress. 185While the overall adoption has been positive and the insights valuable, we've also identified opportunities for improvement. 186 187Based on our findings, we're introducing the following additions, focusing on both the survey-taking experience and the visualization of results: 188 189## ð New 190 191- **AI summaries**: The *Open ended answer view* now offers the option to summarize key themes and sentiment from responses. 192- **Squad Heatmap view**: A new visualization that displays the distribution of priority and sentiment across all participating squads. 193 194## ð Improvements 195
196- **Progress indicator**: Survey-takers can now track their progress and see an estimated completion time. 197- **Navigation system**: Allows users to revisit and edit previous answers or update their anonymity preferences. 198- **Final confirmation**: Users can now review and edit their responses at any time until the survey period officially closes. 199- **Engaging reminders**: Context-based, humorous reminders designed to boost response rates to over 90%. 200 201 `},{name:"Activity Metrics and Anomaly Detection",image:"/landing/activity-metrics.gif",tags:["New Feature","Objective Metrics"],publicationDate:"February 4, 2025",content:` 202 203There's a thing with activity metrics - many people are scared of them. We've talked so much about why measuring individual productivity with LOCs and PR counts is wrong that some now think measuring these things is bad by default. 204 205Data is not bad. Data is data. Activity metrics are useful for detecting outliers and anomalies, preventing burnout, or identifying people who may need extra help or attention. 206 207How you treat the data is what really matters. 208 209## ð New 210 211- **Activity calendar**: Showing metrics like #PRs, #merges, #approvals... 212- **Views by repos, teams, and devs.** 213- **Automatic outlier detection.**: Pullpo automatically detects top and bottom activity outliers, helping prevent burnout and identify people who may need extra help or attention. 214- **Iterations during code reviews.** 215- **Response time on code reviews.** 216 217 `},{name:"DevEx Surveys",image:"/landing/surveys/devex.png",tags:["New Feature","Develeloper Feedback"],publicationDate:"February 3, 2025",content:` 218In recent years, there has been aggressive marketing around developer productivity metrics like DORA, promoting them as the secret key to unlocking development team productivity. 219 220While Pullpo's customers find these metrics valuable for tracking team evolution and benchmarking overall health, metrics alone don't tell us how to improve. 221 222That's why it's crucial to talk with individual developers to understand their daily challenges and main pain points in their jobs. 223 224## ð New 225- **Complete dashboard to analyze responses**: Sentiment analysis, area prioritization. 226- **Complete and short default survey**: Surveys complement and merge perfectly with Pullpo's engineering metrics. 227- **Slack reminders**: Sends personalized DM reminders to developers who haven't responded yet, even with anonymous surveys. 228- **Slack responses**: Developers can reply to the survey directly in Slack. 229 230 `,ctaText:"Learn more",ctaInsideLink:"/products/surveys"}],M={class:"z-10"},E={class:"relative isolate"},G={class:"py-24 lg:pb-40"},H={class:"mx-auto max-w-8xl px-6 lg:px-8"},O={class:"mx-auto max-w-6xl text-center"},V={class:"flex items-center justify-center gap-x-6"},B={class:""},j={class:"mx-auto max-w-6xl pl-[0px] lg:pl-[200px] mt-10 w-full"},J={class:"col-span-2 text-black-light w-full"},U={class:"flex col-span-10 w-full rounded-xl bg-white/5 p-6 ring-1 ring-inset ring-white/10 hover:ring-white/20 hover:bg-white/10 transition cursor-pointer"},Y={class:"text-sm md:text-base leading-7"},$={class:"flex items-center justify-between"},Q={class:"font-semibold text-lg text-white max-w-[500px]"},K={class:"mt-2 flex flex-wrap gap-2"},X=["src"],Z=["innerHTML"],ee={class:"max-w-28 mt-10"},te=["href"],le=D({__name:"index",setup(ie){const o=s(""),k=s(""),d=s(!1),l=s(!1),p=s(!1);R(o,()=>{h()});function h(){return/^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(o.value)?(l.value=!0,!0):(l.value=!1,!1)}async function x(){if(!h()){d.value=!0;return}await N("/office/newIntegrationPetition",{method:z.POST,body:{name:"Viene de CHANGELOG",email:o.value,company_size:"Viene de CHANGELOG",git_provider:"Viene de CHANGELOG",communication_provider:"Viene de CHANGELOG",comments:k.value},authenticated:!1}),p.value=!0}return(_,i)=>{const P=A,C=F;return n(),a("div",null,[r(C,{name:"web"},{default:v(()=>[e("div",M,[e("main",E,[e("div",G,[e("div",H,[e("div",O,[i[2]||(i[2]=e("h1",{class:"text-4xl font-bold tracking-tight text-white sm:text-6xl"},[w(" Our "),e("span",{class:"text-gradient"},"Changelog.")],-1)),i[3]||(i[3]=e("p",{class:"text-white mt-2 mb-3 mx-5 lg:ml-0 text-center text-base sm:text-base"}," Stay updated on the most important updates. ",-1)),e("div",V,[e("div",B,[
230S(e("input",{id:"email","onUpdate:modelValue":i[0]||(i[0]=t=>o.value=t),name:"email",type:"email",placeholder:"[email protected]",autocomplete:"email",class:I([!l.value&&d.value?"ring-2 ring-inset ring-danger focus:ring-danger":p.value?"ring-2 ring-inset ring-success focus:ring-success":"ring-1 ring-inset ring-white/10 focus:ring-2 focus:ring-inset focus:ring-primary","block w-full h-9 rounded-md border-0 bg-white/5 py-1.5 text-white shadow-sm sm:text-sm sm:leading-6"])},null,2),[[T,o.value]])]),r(m,{variant:"primary",super:!0,size:"sm","white-bg":!1,label:"Stay updated",onClick:i[1]||(i[1]=t=>x())})])]),e("div",j,[(n(!0),a(y,null,f(b(q),t=>(n(),a("div",{key:t.name,class:"grid grid-cols-1 gap-6 lg:max-w-none lg:grid-cols-12 mt-10"},[e("div",J,[w(c(t.publicationDate)+" ",1),i[4]||(i[4]=e("div",{class:"w-full h-0.5 bg-black-dark-light rounded-lg hidden lg:block"},null,-1))]),e("div",U,[e("div",Y,[e("div",$,[e("h3",Q,c(t.name),1)]),e("div",K,[(n(!0),a(y,null,f(t.tags,g=>(n(),a("span",{key:g,class:"inline-flex items-center rounded-md bg-pink-400/10 px-2 py-1 text-xs font-medium text-pink-400 ring-1 ring-inset ring-pink-400/20 h-7"},c(g),1))),128))]),t.image?(n(),a("img",{key:0,src:t.image,class:"w-full flex-none rounded-md mt-5","aria-hidden":"true"},null,8,X)):u("",!0),e("div",{class:"prose prose-sm prose-invert mt-5 w-full",innerHTML:b(L)(t.content)},null,8,Z),e("div",ee,[t.ctaInsideLink?(n(),W(P,{key:0,to:t.ctaInsideLink},{default:v(()=>[r(m,{variant:"primary",super:!0,size:"sm","white-bg":!1,label:t.ctaText??""},null,8,["label"])]),_:2},1032,["to"])):u("",!0),t.ctaOutsideLink?(n(),a("a",{key:1,href:t.ctaOutsideLink??""},[r(m,{variant:"primary",super:!0,size:"sm","white-bg":!1,label:t.ctaText??""},null,8,["label"])],8,te)):u("",!0)])])])]))),128))])])])])])]),_:1})])}}});export{le as default};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.