Skip to content

Added perico-543d9a33.md #109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jpchauvel wants to merge 1 commit into from
Closed

Added perico-543d9a33.md #109

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 44 additions & 0 deletions blog/members/perico-543d9a33.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
---
blogpost: true
author: Perico
location: Lima
category: members
language: Español
image: 1
excerpt: 1
---
Comment on lines +1 to +9
Copy link
Contributor

@coderabbitai coderabbitai bot Aug 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Add required date and tighten front matter (title, aliases, language, image/excerpt types).

The note below suggests date is required; add it in front matter. Also consider adding a title, moving aliases to front matter, using a language code, and fixing image/excerpt types to avoid schema issues.

[suggest_optional_refactor]

Apply:

 ---
 blogpost: true
+date: 2025-08-17
+title: "Perico"
 author: Perico
 location: Lima
 category: members
-language: Español
-image: 1
-excerpt: 1
+language: es
+aliases: [perico]
+image: true
+excerpt: "Perfil del miembro Perico de la comunidad Python Perú."
 ---

Notes:

  • If your site uses a slug, consider adding: slug: perico.
  • Confirm the expected values for language (e.g., es vs es-PE) and image (boolean or path).

🏁 Script executed:

#!/bin/bash
set -e

echo "Listing Markdown files in blog/members:"
fd --extension md blog/members | sed -e 's/^/ * /'

echo ""
echo "Selecting an example file (excluding perico):"
example_file=$(fd --extension md blog/members | grep -v perico | head -n1)
echo "Example file: $example_file"

if [ -n "$example_file" ]; then
  echo ""
  echo "Front matter of $example_file (first 20 lines):"
  head -n20 "$example_file"
else
  echo "No other member posts found."
fi

echo ""
echo "Searching for 'aliases:' usage in blog posts:"
rg -n 'aliases:' -t md -C2 blog || true

echo ""
echo "Searching for 'language:' usage in blog posts:"
rg -n 'language:' -t md -C2 blog || true

echo ""
echo "Searching for 'date:' usage in blog posts:"
rg -n 'date:' -t md -C2 blog || true

echo ""
echo "Searching for 'excerpt:' usage in blog posts:"
rg -n 'excerpt:' -t md -C2 blog || true

echo ""
echo "Searching for 'image:' usage in blog posts:"
rg -n 'image:' -t md -C2 blog || true

Length of output: 15385

Add missing publication date and align front matter

The front matter in blog/members/perico-543d9a33.md currently omits a date field, which all other member posts include. Please add a date: YYYY-MM-DD entry (e.g. date: 2025-08-17) immediately after blogpost: true to restore consistency.

Optional improvements—verify these against your project’s schema before applying:
• title: "Perico"
• aliases: [perico]
• slug: perico (to override the autogenerated slug)
• language: use a code (es or es-PE) if supported, otherwise leave as Español
• image: switch from 1 to true or a file path
• excerpt: replace 1 with a descriptive string, e.g. "Perfil del miembro Perico de la comunidad Python Perú."

Confirm field names, types, and ordering with your site’s front-matter spec.

🤖 Prompt for AI Agents 
In blog/members/perico-543d9a33.md around lines 1 to 9, the front matter is
missing a required date field and should be aligned with other member posts;
insert a date entry formatted as YYYY-MM-DD (for example 2025-08-17) immediately
after the blogpost: true line, and optionally validate and update other
front-matter fields to match project schema (e.g., title, aliases, slug,
language code, image as boolean or path, and a descriptive excerpt) ensuring
correct field names, types and ordering.


% NOTA: No olvidar poner la fecha de publicación debajo de `blogpost: true`
Copy link
Contributor

@coderabbitai coderabbitai bot Aug 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Remove the inline note; it will render in the page.

Markdown does not treat this as a comment. Move the date to front matter (see prior suggestion) and delete this line.

-% NOTA: No olvidar poner la fecha de publicación debajo de `blogpost: true`
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
% NOTA: No olvidar poner la fecha de publicación debajo de `blogpost: true`
🤖 Prompt for AI Agents 
In blog/members/perico-543d9a33.md around line 11, remove the inline note line
"% NOTA: No olvidar poner la fecha de publicación debajo de `blogpost: true`"
because Markdown will render it; instead place the publication date in the
file's YAML front matter (add or update a date: YYYY-MM-DD entry) and delete
this inline line so it no longer appears on the page.


# Perico

```{gravatar} perico@gmail.com
---
width: 200
class: "member-gravatar"
---
```

:Aliases: perico

:Ciudad: Lima

## Sobre mí

algo

### ¿Quién eres y a qué te dedicas?

algo

### ¿Cómo programas en Python?

algo

### ¿Tienes algún aporte a la comunidad de Python?

algo

### ¿Estás disponible para hacer mentoring, consultorías, charlas?

algo