You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update `@types/ms` resolution to version 0.7.32 in `package.json` and `yarn.lock`.
Add ts-node script and update linting commands in package.json and lint.sh.
Enhance CI workflow with debug info for PR events; add new blog post template and assets.
Refactor types in find-markdown.ts and add test PR event JSON file.
Refactor PR file handling: update to use 'files' instead of 'added_files' for added file tracking in GitHub Actions. Adjust test data accordingly.
Remove debug logging and add base branch environment variable in workflows
Enhance GitHub Actions workflow: add branch info echo and ensure make step before linting.
Refactor linting scripts and update pull request workflow
- Removed lint step from GitHub Actions workflow
- Simplified the `find-markdown.ts` script by removing GHA-related functionality
- Updated `getGitModifiedFiles` to accept a base branch parameter
- Resolved types and streamlined logic for markdown file detection
- Adjusted lint scripts to handle modes more effectively
Update markdown linting script to exclude 'node_modules' directory and add debug logging functionality in the linting process. Set DEBUG mode to off by default.
Update GitHub Actions workflow and improve file detection logic
- Upgraded `actions/checkout` from v2 to v4 and set fetch depth.
- Enhanced `getGitModifiedFiles` function to handle both local and GitHub Actions environments.
- Improved error handling and added debug logging for file detection.
Refactor GitHub Actions workflow and TypeScript script for enhanced efficiency and clarity in fetching branches and modified files.
# See the blogging docs at https://github.com/pulumi/docs/blob/master/BLOGGING.md
55
+
# for details, and please remove these comments before submitting for review.
56
+
---
57
+
58
+
What you put here will appear on the index page. In most cases, you'll also want to add a Read More link after this paragraph (though technically, that's optional. To do that, just add an HTML comment like the one below.
59
+
60
+
<!--more-->
61
+
62
+
And then everything _after_ that comment will appear on the post page itself.
63
+
64
+
Either way, avoid using images or code samples [in the first 70 words](https://gohugo.io/content-management/summaries/#automatic-summary-splitting) of your post, as these may not render properly in summary contexts (e.g., on the blog home page or in social-media previews).
65
+
66
+
## Writing the Post
67
+
68
+
For help assembling the content of your post, see [BLOGGING.md](https://github.com/pulumi/docs/blob/master/BLOGGING.md). For general formatting guidelines, see the [Style Guide](https://github.com/pulumi/docs/blob/master/STYLE-GUIDE.md).
69
+
70
+
## Code Samples
71
+
72
+
```typescript
73
+
let bucket =newaws.s3.Bucket("stuff");
74
+
...
75
+
```
76
+
77
+
## Images
78
+
79
+

80
+
81
+
## Videos
82
+
83
+
{{< youtube "kDB-YRKFfYE?rel=0" >}}
84
+
85
+
Note the `?rel=0` param, which tells YouTube to suggest only videos from same channel.
0 commit comments