search

supermomo668 / test-git

0 stars 0 forks source link

Test Repo Set-up #5

Open supermomo668 opened 7 months ago

supermomo668 commented 7 months ago

Require to add additional workflows to ensure CI/CD integrity

supermomo668 commented 7 months ago

The cause of the issue is likely to be the lack of sufficient workflows to ensure the integrity of the Continuous Integration/Continuous Deployment (CI/CD) process in the project.

The suggested solution is to add additional workflows that cover all aspects of the project. This could include workflows for building the project, running tests, deploying the project, and any other tasks that are necessary for the project. These workflows should be added to the .github/workflows directory in the repository. Each workflow should be defined in a separate YAML file, and should be triggered by the appropriate events (such as push or pull request events).

The relevant resources you may look into are the GitHub Actions documentation, which provides detailed information on how to create and manage workflows. Additionally, the GitHub Actions workflow syntax page provides a reference for the syntax used in workflow files.

You may also want to look into the commit from mikepsinn/FDAi that enabled testing via GitHub actions for an example of a workflow file.

supermomo668 commented 7 months ago

Require to add additional workflows to ensure CI/CD integrity. Any suggestions?

github-actions[bot] commented 7 months ago

I'm sorry, Matt, but I don't have the specific GitHub issue that you're referring to. Could you please provide more details or context about the issue that needs to be resolved? This will help me provide a more accurate and helpful response. Context:

contributing

For Non-Technical Users:

  1. Editing Documentation via GitHub's Online Editor:

    • Navigate to the file you want to edit in your forked repository on GitHub.
    • Click on the pencil icon (Edit this file) in the top right corner of the file view.
    • Make your changes in the editor.
    • At the bottom of the page, describe your changes and click Commit changes.

  2. Using GitHub Issues and Discussions:

    • Navigate to the Issues or Discussions tab in the main FDAi repository.
    • You can create a new issue/discussion or contribute to an existing one.

      README

      Getting Involved

If you are a developer interested in contributing to the FDAi project, here are some steps to get started:

  1. Introduce yourself by creating a Markdown page within this folder with your name or your organization's name as the filename.
  2. On your page, include:
    • An introduction of yourself or your organization.
    • Your role and interest in the FDAi project.
    • Contact information or how you wish to be engaged.
  3. Review open issues in the repository's issue tracker to see if there are any tasks or discussions you can contribute to.
  4. Propose new ideas or projects by opening a new issue or submitting a project proposal using the provided template in the /templates directory.

    SECURITY

    Reporting a Vulnerability

To report a security vulnerability within the FDAi project, follow these steps:

  1. Do not open a public issue on GitHub.
  2. Email security@FDAi.earth with the subject "FDAi Security Vulnerability".
  3. In the email, include a detailed description of the vulnerability, along with the affected component(s) and version(s) of the project.
  4. Optionally, provide a proof of concept, screenshots, or any other relevant information to help us understand and reproduce the issue.

The security team will acknowledge receipt of your vulnerability report within 48 hours and will provide an estimated timeline for addressing the issue. Once the vulnerability has been resolved, the security team will coordinate with you to disclose the issue publicly, if appropriate.

README

What You Will Find Here

In this directory, you will find a variety of resources that can help you understand the project's technical aspects, coding practices, and other relevant guidelines. These resources are meant to assist you in creating contributions that align with the project's standards and objectives.

For any questions or assistance, please refer to the CONTRIBUTING.md file or use the GitHub issue tracker to reach out to the FDAi community.

Thank you for being a part of the FDAi initiative. Your collaboration is vital to the success of this project.

supermomo668 commented 6 months ago

what is the top maintenance issue to address in the FDAi repository at the moment?

supermomo668 commented 6 months ago

what is the top maintenance issue to address in the FDAi repository at the moment?