Merge branch 'main' into fix/PullRequestGuide
This commit is contained in:
Henrik Helgesen
GitHub
commit
8448724c3c
3 changed files with 74 additions and 77 deletions
12
README.md
12
README.md
|
|
@ -1,14 +1,8 @@
|
|||
# Project
|
||||
# Business Central Design Patterns & Best Practices
|
||||
|
||||
> This repo has been populated by an initial template to help get you started. Please
|
||||
> make sure to update the content to build a great experience for community-building.
|
||||
This site is meant to house some of the community's knowledge about Microsoft Dynamics 365 Business Central AL Development best practices, particularly around hosting Design Patterns.
|
||||
|
||||
As the maintainer of this project, please make a few updates:
|
||||
|
||||
- Improving this README.MD file to provide a great experience
|
||||
- Updating SUPPORT.MD with content about this project's support experience
|
||||
- Understanding the security reporting process in SECURITY.MD
|
||||
- Remove this section from the README
|
||||
Please see the [ALGuidelines.dev](https://alguidelines.dev/) site for the full information about this project.
|
||||
|
||||
## Contributing
|
||||
|
||||
|
|
|
|||
|
|
@ -1,60 +1,60 @@
|
|||
+++
|
||||
chapter = true
|
||||
pre = "<b><i class='fas fa-clone'></i> </b>"
|
||||
title = "Guide to Fork & PR"
|
||||
weight = 100
|
||||
+++
|
||||
|
||||
## Abstract
|
||||
|
||||
AL Guidelines is a community project, and as such YOU are encouraged to submit corrections and new ideas. In order to get your content included, you must submit a pull request to the GitHub Repository (Located here: https://github.com/microsoft/alguidelines). All Pull Requests are subject to approval by a minimum of three admins.
|
||||
|
||||
If You are toying with an idea, but You aren't ready to create a document just yet, you are encouraged to create a project discussion thread here: https://github.com/microsoft/alguidelines/discussions
|
||||
|
||||
{{% notice warning %}}
|
||||
If You haven't worked in collaboration with "external" GitHub repositories before, please familiarize yourself with that process by visiting:
|
||||
|
||||
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests
|
||||
|
||||
{{% /notice %}}
|
||||
|
||||
## Steps
|
||||
Now that You have decided that You are ready to contribute, these are the steps to take.
|
||||
{{% notice info %}}
|
||||
You can read more about this process here:
|
||||
|
||||
https://docs.github.com/en/get-started/quickstart/contributing-to-projects
|
||||
{{% /notice %}}
|
||||
|
||||
### Step 1: Fork
|
||||
In order to work on the repository, You must [Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) the repository.
|
||||
|
||||
By forking the repository, You essentially create a copy into Your own account.
|
||||
|
||||
Start by going to the GitHub Repository (https://github.com/microsoft/alguidelines), and press the Fork 
|
||||
|
||||
Once You have successfully forked the repository, go to your own GitHub repository : 
|
||||
|
||||
You are now able to clone your own repository to your local pc and start editing using your favorite editor. [Visual Studio Code](https://code.visualstudio.com/) is perfectly fine for this task.
|
||||
|
||||
{{% notice info %}}
|
||||
You can read more about forking here:
|
||||
|
||||
https://docs.github.com/en/get-started/quickstart/fork-a-repo
|
||||
{{% /notice %}}
|
||||
|
||||
### Step 2: Branch
|
||||
While not necessarily a must, it is always good practice to create a branch off of your forked repository. That will allow you to work on multiple contributions at the same time and won't have to wait for pull requests to be approved before you can continue on your next contribution.
|
||||
|
||||
{{% notice info %}}
|
||||
You can read more about Branches here:
|
||||
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches
|
||||
{{% /notice %}}
|
||||
### Step 3: Pull Request
|
||||
Once you are happy with your contibution, it's time to create a pull request to propose changes into the main project! This is the final step in producing a fork of someone else's project, and arguably the most important. If you've made a change that you feel would benefit the community as a whole, you should definitely consider contributing back.
|
||||
|
||||
To do so, head on over to the repository on GitHub where your project lives. For this example, it would be at `https://www.github.com/<your_username>/alguidelines`. You'll see a banner indicating that your branch is one commit ahead of microsoft:main. Click **Contribute** and then **Open a pull request.**
|
||||
|
||||
GitHub will bring you to a page that shows the differences between your fork and the microsoft/alguidelines repository. Click **Create pull request.**
|
||||
|
||||
GitHub will bring you to a page where you can enter a title and a description of your changes. _It's important to provide as much useful information and a rationale for why you're making this pull request in the first place._ The project owners needs to be able to determine whether your change is as useful to everyone as you think it is. Finally, click **Create pull request.**
|
||||
+++
|
||||
chapter = true
|
||||
pre = "<b><i class='fas fa-clone'></i> </b>"
|
||||
title = "Guide to Fork & PR"
|
||||
weight = 100
|
||||
+++
|
||||
|
||||
## Abstract
|
||||
|
||||
AL Guidelines is a community project, and as such YOU are encouraged to submit corrections and new ideas. In order to get your content included, you must submit a pull request to the GitHub Repository (Located here: https://github.com/microsoft/alguidelines\). All Pull Requests are subject to approval by a minimum of three admins.
|
||||
|
||||
If You are toying with an idea, but You aren't ready to create a document just yet, you are encouraged to create a project discussion thread here: https://github.com/microsoft/alguidelines/discussions
|
||||
|
||||
{{% notice warning %}}
|
||||
If You haven't worked in collaboration with "external" GitHub repositories before, please familiarize yourself with that process by visiting:
|
||||
|
||||
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests
|
||||
|
||||
{{% /notice %}}
|
||||
|
||||
## Steps
|
||||
Now that You have decided that You are ready to contribute, these are the steps to take.
|
||||
{{% notice info %}}
|
||||
You can read more about this process here:
|
||||
|
||||
https://docs.github.com/en/get-started/quickstart/contributing-to-projects
|
||||
{{% /notice %}}
|
||||
|
||||
### Step 1: Fork
|
||||
In order to work on the repository, You must [Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) the repository.
|
||||
|
||||
By forking the repository, You essentially create a copy into Your own account.
|
||||
|
||||
Start by going to the GitHub Repository (https://github.com/microsoft/alguidelines), and press the Fork 
|
||||
|
||||
Once You have successfully forked the repository, go to your own GitHub repository : 
|
||||
|
||||
You are now able to clone your own repository to your local pc and start editing using your favorite editor. [Visual Studio Code](https://code.visualstudio.com/) is perfectly fine for this task.
|
||||
|
||||
{{% notice info %}}
|
||||
You can read more about forking here:
|
||||
|
||||
https://docs.github.com/en/get-started/quickstart/fork-a-repo
|
||||
{{% /notice %}}
|
||||
|
||||
### Step 2: Branch
|
||||
While not necessarily a must, it is always good practice to create a branch off of your forked repository. That will allow you to work on multiple contributions at the same time and won't have to wait for pull requests to be approved before you can continue on your next contribution.
|
||||
|
||||
{{% notice info %}}
|
||||
You can read more about Branches here:
|
||||
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches
|
||||
{{% /notice %}}
|
||||
### Step 3: Pull Request
|
||||
Once you are happy with your contibution, it's time to create a pull request to propose changes into the main project! This is the final step in producing a fork of someone else's project, and arguably the most important. If you've made a change that you feel would benefit the community as a whole, you should definitely consider contributing back.
|
||||
|
||||
To do so, head on over to the repository on GitHub where your project lives. For this example, it would be at `https://www.github.com/<your_username>/alguidelines`. You'll see a banner indicating that your branch is one commit ahead of microsoft:main. Click **Contribute** and then **Open a pull request.**
|
||||
|
||||
GitHub will bring you to a page that shows the differences between your fork and the microsoft/alguidelines repository. Click **Create pull request.**
|
||||
|
||||
GitHub will bring you to a page where you can enter a title and a description of your changes. _It's important to provide as much useful information and a rationale for why you're making this pull request in the first place._ The project owners needs to be able to determine whether your change is as useful to everyone as you think it is. Finally, click **Create pull request.**
|
||||
|
|
|
|||
|
|
@ -1,11 +1,14 @@
|
|||
<a id="logo" href="{{ .Site.Params.landingPageURL | default " /" | relLangURL }}" style="
|
||||
color: #f5f5f5;
|
||||
font-family: 'Novacento Sans Wide', 'Helvetica', 'Tahoma', 'Geneva', 'Arial', sans-serif;
|
||||
font-size: 30px;
|
||||
font-weight: bold;
|
||||
margin-top: -2px;
|
||||
">
|
||||
<a id="logo"
|
||||
href="{{ .Site.Params.landingPageURL | default "/" | relLangURL }}"
|
||||
style="
|
||||
color: #f5f5f5;
|
||||
font-family: 'Segoe UI Semibold', 'Segoe UI', SegoeUI, 'Helvetica Neue', Helvetica, Arial, sans-serif;
|
||||
font-size: 30px;
|
||||
font-weight: 300;
|
||||
margin-top: -2px;
|
||||
">
|
||||
|
||||
ALGuidelines.Dev
|
||||
</a>
|
||||
|
||||
<i style="color: #f5f5f5;">Code is Poetry</i>
|
||||
<i style="color: #f5f5f5;">Code is Poetry ...</i>
|
||||
Loading…
Add table
Add a link
Reference in a new issue