This project welcomes contributions and suggestions. Most contributions require you to
Sign in to like and favorite skills
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
Important: when translating text in this repo, please ensure that you do not use machine translation. We will verify translations via the community, so please only volunteer for translations in languages where you are proficient.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information read the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
Please do not open GitHub issues for general support questions as the GitHub list should be used for feature requests and bug reports. This way we can more easily track actual issues or bugs from the code and keep the general discussion separate from the actual code.
Whenever you are submitting any changes to the Generative AI for Beginners repository, please follow these recommendations.
[]()./../?&wt.mc_id=WT.mc_id=?&wt.mc_id=WT.mc_id=/en-us//en/./imagesWhen you submit a pull request, four different workflows will be triggered to validate the previous rules. Simply follow the instructions listed here to pass the workflow checks.
This workflow ensures that any relative path in your files is working. This repository is deployed to GitHub pages so you need to be very careful when you type the links that glue everything together to not direct anyone to the wrong place.
To make sure that your links are working properly simply use VS code to check that.
For example, when you hover over any link in your files you will be prompted to follow the link by pressing on ctrl + click
If you click on a link and it's not working locally then, surely it will trigger the workflow and won't work on GitHub.
To fix this issue, try to type the link with the help of VS code.
When you type
./../
Follow the path by clicking on the desired file or folder and you will be sure that your path is not broken.
Once you add the correct relative path, save, and push your changes the workflow will be triggered again to verify your changes. If you pass the check then you are good to go.
This workflow ensures that any relative path has tracking in it. This repository is deployed to GitHub pages so we need to track the movement between the different files and folders.
To make sure your relative paths have tracking in them simply check for the following text
?wt.mc_id=If not, you may get the following error.
To fix this issue, try to open the file path that the workflow highlighted and add the tracking ID to the end of the relative paths.
Once you add the tracking ID, save, and push your changes the workflow will be triggered again to verify your changes. If you pass the check then you are good to go.
This workflow ensures that any web URL has tracking in it. This repository is available to everyone so you need to make sure to track the access to know from where the traffic is coming.
To make sure your URLs have tracking in them simply check for the following text
?wt.mc_id=If not, you may get the following error.
To fix this issue, try to open the file path that the workflow highlighted and add the tracking ID to the end of the URLs.
Once you add the tracking ID, save, and push your changes the workflow will be triggered again to verify your changes. If you pass the check then you are good to go.
This workflow ensures that any web URL doesn't have country specific locale in it. This repository is available to everyone around the world so you need to make sure not to include your country's locale in URLs.
To make sure your URLs don't have country locale in them simply check for the following text
/en-us//en/If not, you may get the following error.
To fix this issue, try to open the file path that the workflow highlighted and remove the country locale from the URLs.
Once you remove the country locale, save, and push your changes the workflow will be triggered again to verify your changes. If you pass the check then you are good to go.
Congratulations! We will get back to you as soon as possible with feedback about your contribution.