ipoetdev/ibm-skills-ai-colab-sessions

PORTFOLIO: IBM Skills Build Programme for Artificial Intelligence - CoLab - Live Sessions & Final Project

ibm-skills-ai-colab-sessions's Issues

[Task] 🛠️ Security: Configure security analysis: Private Vuln Reporting | Dependabot

Task Topic

Other

Task Description

Configure repository security and analysis using GitHub Secuirty Settings

Tasks

• Private vulnerability reporting
• Dependency graph
• Automatic dependency submission
• Dependabot
  • Dependabot alerts
    • Dependabot rules
  • Dependabot security updates
  • Grouped security updates
  • Dependabot version updates
  • Dependabot on Actions runners

Code scanning

Tools

• CodeQL analysis
• Other Tools
  • Add any third-party

Protection Rules

• Security alert severity levels: High or Higher
• Standard alert severity level: Only Errors

Secret scanning

• Receive alerts on GitHub for detected secrets, keys, or other tokens.
• Push protection: Block commits that contain supported secrets

Use Case

Outline: Security and analysis features help keep your repository secure and updated.

• Enable these features to perform read-only analysis on your repository.

Additional Information

• https://github.com/iPoetDev/ibm-skills-ai-colab-sessions/security
• https://github.com/iPoetDev/ibm-skills-ai-colab-sessions/settings/security_analysis

🐛 [Bug]: External | OpenAI bug with API Key generation

Current Behavior

Current: OpenAI keys are not being generated.

Inspect | DevConsole

Expected Behavior

Expect: API Key generated on OpenAI on https://platform.openai.com/api-keys

Steps to Reproduce

1. Open in 1st Browser and attempt
2. Open in 2nd Browser (Google Chrome) and attempt
3. Open in 2nd Browser (Google Chrome, incognito) and attempt
4. Open in Google Chrome on mobile on 3G and attempt

Environment

• OS: Windows, Android
• MS Edge, Chrome, Chrome fro Android

Anything else?

No response

FAIR Compliance Dashboard

Check the FAIRness of your software

This issue is your repository's dashboard for all things FAIR. Keep it open as making and keeping software FAIR is a continuous process that evolves along with the software. You can read the documentation to learn more.

LICENSE ✔️

A LICENSE file is found at the root level of the repository.

Metadata ✔️

A CITATION.cff and a codemeta.json file are found in the repository. They may need to be updated over time as new people are contributing to the software, etc.

📝 [Docs]: Build out the Repositories GitHub Issue Templates using GitHub Issue Forms

Docs Context

Configuration

File Name

.yaml (see below)

File Path

.github/ISSUE_TEMPLATES

Location

Templates

Type of Change

New/Missing

RFC Outline

Request:

• Design, prepare and deploy GitHub YAML forms for the following use cases.
• Why:
  • a) Show case knowledge, skill and refinement in issue definition and management,
  • b) Provide continual improvement and issue tracking facilities to repository and project.
  • c) Dog food and use these methods/approaches and use this as a task list.

Files:

• bug.yaml: Code Issues: For reporting bugs or unexpected behavior in the code.
• docs.yaml: Documentation RFC: For requesting changes or updates to documentation.
• question.yaml: Support Request: For users seeking help or clarification on using the project.
• feature.yaml: Feature Request: For suggesting new features or enhancements.
• task.yaml: Task: For tracking specific tasks, chores, minor that need to be completed.
• security.yaml: Security Reports: For tracking security issue like, libary versioning, dependancybot, secret exposure, CVEs that need to be reported.

_{1: Yaml created/generated using Perplexity.ai}

Additional Information

.

Sources:

• ¹ Perplexity.ai (2024) "List the best practice and all types of issue templates types and pull request template types for GitHub", Last Access: July 2024
• ² GitHub.com (2024) "Issues and PR Templates: Syntax for Issue Forms, GitHub.com", Last Access, July 2024
• ³ GitHub.com (2024) "Issues and PR Templates: Syntax for GitHub's form schema", Last Access, July 2024

[Task] 🛠️ Chore | Enhancement: Automate and generate Labels from `yaml` for Issues and PRs.

Task Topic

Automations

Task Description

Request: Automate and generate Labels from yaml configuration files in lieu of the burden of manual definition, creation, editing, removal.

How: By a GitHub Action

• GitHub Action
• GitHub App
• External Service

1. Select from GitHub Marketplace
2. Select from other GitHub action source
3. Roll your own action.

Use Case

Problem to Solve

• Manually re-creating labels per repository
• Customising longer inventory of labels
• Utilising labels for more descriptive context / categorisation for search and individual preference.
• Utilising labels to automate workflow and issue lifecycle (state, status, stage, priority, severity).

User Story

Context	Description
As a	maintainer of a GitHub repository
I/we want	to manage the lifecycle of issues by workflow automation
So that	to reduce manual effort in creating, reading/defining context, modifying, and removing or deprecating

Additional Information

Proposed Global Candidate Labels

Name	Color	Description	Aliases
✨ good first issue	5319e7	✨ Good for newcomers	beginner, easy
🆘 help wanted	008672	🆘 Extra attention is needed	assistance, need help
⏳ status: pending	c5def5	⏳ More info is needed before deciding what to do	awaiting response, waiting
📌 status: pinned	0052cc	📌 Should not be labeled as stale	important, 🛑 dont close
🕰️ status: stale	fbca04	🕰️ Inactive issues and PRs	stale
🚫 status: wontfix	cfd3d7	🚫 This will not be worked on	wontfix, not going to fix
🐛 type: bug	d73a4a	🐛 Verified problems that need to be worked on	bug, defect
🔧 type: chore	C5DEF5	🔧 Code changes: refactoring, dependency changes	dependencies, type: dependencies, automation, type: automation
📚 type: docs	C5DEF5	📚 Documentation changes	documentation, maintenance, type: maintenance
🔄 type: duplicate	cfd3d7	🔄 This issue or pull request already exists	duplicate, already reported
🌟 type: feature	0E8A16	🌟 New feature or feature request	enhancement, type: enhancement, new feature
🔧 type: fix	1D76DB	🔧 Updates to existing functionalities	fix, improvement
❌ type: invalid	e4e669	❌ This doesn't seem right	invalid, not valid
🚫 type: not a bug	0e8a16	🚫 Reports that happen not to be our fault	not a bug, not an issue
❓ type: question	d876e3	❓ Further information is requested	question, inquiry
🔍 type: enhancement	0E8A16	🔍 Improvements to existing features	improvement, feature enhancement
🔬 type: research	f9c2ff	🔬 Research tasks or investigations	investigation, exploration
⚙️ type: performance	ffcc00	⚙️ Performance-related issues or improvements	performance issue, optimization

Priority Labels

Name	Color	Description	Aliases
🚨 priority: high	ff0000	🚨 High priority - needs immediate attention	urgent, critical
⚠️ priority: medium	ffcc00	⚠️ Medium priority - should be addressed soon	normal, moderate
🟢 priority: low	00ff00	🟢 Low priority - can be addressed later	minor, trivial

Severity Labels

Name	Color	Description	Aliases
🔥 severity: critical	ff0000	🔥 Critical severity - major impact on functionality	blocker, severe
⚠️ severity: major	ffcc00	⚠️ Major severity - significant impact but not critical	high impact
🟢 severity: minor	00ff00	🟢 Minor severity - low impact on functionality	low impact, negligible
🔵 severity: trivial	c5def5	🔵 Trivial severity - no significant impact	cosmetic, insignificant

[Feature] 🚀 Anthropic Text Completions + API

Feature Topic

Jupyter Notebooks

Feature Description

In Fixing #7 ,We port to Anthropic text completions, API and Python SDK.

Use Case

Fixes #7, and for the same use case: Demonstrate TextCompletions as part of embeddable AI solutions

Additional Information

No response

Sources and References

• #7