File: DEVELOP.md

package info (click to toggle)
libmail-dmarc-perl 1.20240314-1
  • links: PTS
  • area: main
  • in suites: sid, trixie
  • size: 1,852 kB
  • sloc: perl: 4,944; xml: 13; makefile: 10; sh: 1
file content (56 lines) | stat: -rw-r--r-- 1,749 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
# Find the source

[The source code is hosted on GitHub](https://github.com/msimerson/mail-dmarc)


# Download the source

To make changes or submit patches, visit the GitHub URL and click the ***Fork*** button. Then clone your fork to your local disk:

    git clone git@github.com:YOUR-USER-NAME/mail-dmarc.git


# Use the source

Use git in the normal way:

    cd mail-dmarc
    .... make a change or two ...
    git status       ( see changes )
    git diff         ( show diffs  )
    git add ...      ( stage changes )
    git commit

If your changes are significant and might possibly involve more than one commit, create a branch first:

    git checkout -b fix-knob-handle
    ... make changes ...
    git commit
    ... make more related changes ...
    git commit

When you are done making changes, push them to GitHub:

    git push origin     (push to your GitHub account)

When the new feature branch is no longer useful, delete it:

    git branch -d fix-knob-handle

# Submit your changes

    git push origin master    (push to your GitHub account)

Visit your fork on the GitHub web site. On the main page of your fork is a ***Pull Request*** button. That is how you submit your changes to the main repo. A collaborator will review your PR and either comment or merge it.

# Check build status:

[![Build Status](https://github.com/msimerson/mail-dmarc/actions/workflows/ci.yml/badge.svg)](https://github.com/msimerson/mail-dmarc/actions/workflows/ci.yml)

GitHub Actions automatically runs build tests when commits are pushed to GitHub, and sends notifications to the author(s) in case of failure. For everyone else, checking the build status after a push request is merged is a good idea.

# Release

````sh
.release/do.sh
````