The issue you shared appears to be a simple request asking for two things:
- A link to a GitHub release (example: v0.1.0).
- A software icon (likely a badge or logo to display in the README or project page).
The comment Bien sûr 😂 Voici les deux : is likely a reply from someone who already provided them, but the placeholders (/) haven't been filled in yet – meaning the actual link and icon might still be missing.
What you might need to do
If this is your issue or you’re the project maintainer, you can resolve it by:
- Creating a release on GitHub (if you haven't already):
· Go to your repository → Releases → Draft a new release.
· Choose a tag (e.g., v0.1.0), add a title/description, and publish.
· The URL will be: https://github.com/your-username/your-repo/releases/tag/v0.1.0
- Adding a software icon – common ways:
· Use a badge from shields.io (e.g., a “release” badge or a custom logo).
· Place an icon/logo image in your README (e.g., using an ![]()
tag or Markdown).
· If you mean a desktop/application icon, you’d add it to your project’s assets.
- Updating the issue:
· Once done, paste the real release link and the icon (or a link to it) in a comment.
· Then close the issue (if everything is satisfied).
If you’re not the owner
This might be a feature request or a reminder for the maintainer. You can gently ping them or, if you have permissions, you can create the release and icon yourself and then close the issue.
Does this cover what you needed? If you were asking something else (e.g., how to use @copilot assignments, or what the issue means), just let me know and I’ll clarify further.
The issue you shared appears to be a simple request asking for two things:
The comment Bien sûr 😂 Voici les deux : is likely a reply from someone who already provided them, but the placeholders (/) haven't been filled in yet – meaning the actual link and icon might still be missing.
What you might need to do
If this is your issue or you’re the project maintainer, you can resolve it by:
· Go to your repository → Releases → Draft a new release.
· Choose a tag (e.g., v0.1.0), add a title/description, and publish.
· The URL will be: https://github.com/your-username/your-repo/releases/tag/v0.1.0
· Use a badge from shields.io (e.g., a “release” badge or a custom logo).
· Place an icon/logo image in your README (e.g., using an
· If you mean a desktop/application icon, you’d add it to your project’s assets.
· Once done, paste the real release link and the icon (or a link to it) in a comment.
· Then close the issue (if everything is satisfied).
If you’re not the owner
This might be a feature request or a reminder for the maintainer. You can gently ping them or, if you have permissions, you can create the release and icon yourself and then close the issue.
Does this cover what you needed? If you were asking something else (e.g., how to use @copilot assignments, or what the issue means), just let me know and I’ll clarify further.