* add #handbook label to handbook PRs
* Update get-is-pr-only-handbook-changes.js
* remove while loop from _.all()
* revert changes to github token name
* Simplifications
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
A timeboxed workaround for an intermittent issue where the mergefreeze API reports that a repo is frozen: false, when the mergefreeze UI says that it is actually truly frozen.
Turns out the issue being debugged in https://github.com/fleetdm/fleet/pull/6906 was in the API itself-- somehow it can get stuck on frozen: false. If that happens, the solution is to freeze/unfreeze everything in the dashboard
* Tool: Bring back mergefreeze API integration
Context: https://github.com/fleetdm/fleet/pull/5628#issuecomment-1196175485
Unfortunately, the API doesn't work.
* Lay out how this would work in the database - but instead, do it ephemerally for now
* Remove model
* Maintain state (the easy way for now)
* Website: Follow up to strip leading slashes
re https://github.com/fleetdm/fleet/pull/6796#issuecomment-1193054810
* remove log
* Verified: whitespace trim not needed
And leading slash trim is only needed if using a regex route (not something I recommend most of the time). But since we are using one, I included it, and put it in all three places for consistency. (It doesn't ever hurt)
* Simplify regex syntax used for #2025
* extra trailing slashes now redirect instead of rendering
* Simplify regex
* Match implementation to view-basic-documentation, etc
* Match view-basic-documentation, and slurp up title and description logic to help indicate (and future proof) that it has no side effects
* Update view-basic-handbook.js
* Update view-basic-documentation.js
* trivial
* lint fix
* make handbook and doc landing pages continue working despite my recent commit in this same PR, and add some comment clarifications
* update regex to replace leading slashes and whitespace
Co-authored-by: Eric <eashaw@sailsjs.com>
Related to #5898, this reports an anonymized summary of errors stored in Redis into the analytics payload.
For each error stored, this includes:
- A `count` attribute with the number of occurrences of the error
- A `loc` attribute with the 3 topmost lines in the stack trace. Note that stack traces only contain package name + line number (example: github.com/fleetdm/fleet/server.go:12
This also includes a minor refactor around error types.
* Website: Create page for sales one-pager
* update layout, add images
* update mobile layout
* update layout & styles
* Update sales-one-pager.less
* add todos for page description and page title
* add alt text, final route & meta information, make hero-image visible at 1024px
* state of device management page, chart component
* add images
* website: add charts.min.js, update layout, page script, and images
* layout updates, component validation
* add alt text, lint fixes
* update image name
* update bar-chart styles and layout
* add empty href and link styles
* Style overrides for mobile & tablet
• Added style overrides for mobile and tablet.
* Updated text
Updated text for the following sections:
• Introduction
• Key findings
• Part 1
* Updated text
Updated text in the following sections:
• Part 2
• Part 3
• Part 4
• Part 5
• Part 6
* Additional icon and text change
• Added icon for GitOps
• Repositioned text: The future of device management
* Text change
Removed "Takeaways" header from Part 6.
* style changes
• fixed some inconsistent headers (h3 to h2).
• fixed margin bottom on new GitOps note.
• Removed unneeded subsection div after removing "Takeaways" heading in my previous commit.
* update chart styles, add update charts function, sticky navigation
* lint fix
* lint fix
* Scroll navigation with header
* text changes
Updated chart titles to match the survey.
* style tweaks
Style tweaks to the charts.
* add pdf
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
* trivial (comments)
* Remove old unfreeze/freeze logic
* trivial (clarify comment)
* Trivial (fix weird character)
* Extrapolate DRI mappings into config.
* Explain why this exists
* Extrapolate logic
* Use extrapolated logic + add 5 second wait time to prevent accidents + clean up
* Use extrapolated logic and fix omission in helper
* Make freezing actually happen and document usage
* In script, don't freeze PRs as long as they're preapproved to be edited by SOMEBODY
* Lint fixes
* articles page
* update articles route to handle category urls
* update articles page
* add articleImageUrl meta tags to article pages
* basic empty state, add comments
* Update view-articles.js
* Update articles.less
* add articles, update styles and image url validation
* lint fix
* Update routes.js
* Update articles.ejs
* Update articles.page.js
Updated article category descriptions.
* migrated more articles
I migrated more articles so that all categories are populated.
* Added thumbnails to new posts
* Some style tweaks
- Tweaked a couple of styles
- Added cursor: pointer to filters
- Changed "Blog" to "Articles" in the navigation
- Changed /blog to /articles in the navigation
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
* add custom blockquote render and styles
* Update to-html.js
* adjust margin, replace icon
* increase margin on image
* Style updates
After seeing it in action, I noticed some improvements. I also updated Figma to reflect.
• Changed colors and icon alignment
• Adjusted top/bottom margins
• Adjusted corner radius
• Added new color variable (existing in Figma) to colors.less
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
* Github bot: Temporarily disable label change notifications
Michael Thomas🕐 Today at 01:36
Are these alerts necessary in #g-digital-experience, and if not, how do we turn them off? They're creating a lot of noise in the channel 😵
1 reply
mikermcneil 3 minutes ago
I'm envisioning Digital Experience is responsible for keeping github labels tidy, so having visibility into changes would be useful. If you currently don't have bandwidth to do it, this is an easy thing to let slip, since it isn't the highest priority. (Labels have already gotten a bit messy- to the point I don't use them at all anymore, for example. I don't think they're actually necessary anymore, other than for doing estimations)
I'll PR a change that disables it for now.
* fix extra ampersand
