script to pull github activity report

 import os

import requests

import csv

from datetime import datetime


# Configuration

REPO = 'username/reponame'  # Repository name

START_DATE = '2023-09-03T00:00:00Z'  # Start of the date range

END_DATE = '2023-11-13T23:59:59Z'  # End of the date range

GITHUB_TOKEN = os.getenv('GITHUB_TOKEN')  # Retrieve GitHub token from environment variable


headers = {

    "Authorization": f"token {GITHUB_TOKEN}",

    "Accept": "application/vnd.github.v3+json"

}


output_file = 'github_report.csv'


def fetch_commits():

    """Fetch commits within the specified date range."""

    url = f'https://api.github.com/repos/{REPO}/commits'

    params = {

        'since': START_DATE,

        'until': END_DATE,

    }

    response = requests.get(url, headers=headers, params=params)

    commits = response.json()

    

    commit_data = []

    for commit in commits:

        date = commit['commit']['author']['date'][:10]  # Extract only YYYY-MM-DD

        message = commit['commit']['message'][:100]  # Limit message to 100 characters

        commit_time = commit['commit']['author']['date']

        commit_data.append((date, message, commit_time, commit_time, 0))  # Commits have same start and end time


    return commit_data


def fetch_issues():

    """Fetch issues (including bugs) created within the specified date range."""

    url = f'https://api.github.com/repos/{REPO}/issues'

    params = {

        'since': START_DATE,

        'state': 'all'

    }

    response = requests.get(url, headers=headers, params=params)

    issues = response.json()


    issue_data = []

    for issue in issues:

        created_at = issue['created_at'][:10]  # Extract only YYYY-MM-DD

        if START_DATE <= issue['created_at'] <= END_DATE:

            title = issue['title'][:100]  # Limit title to 100 characters

            created_time = issue['created_at']

            closed_time = issue.get('closed_at', created_time)  # Use created time if not closed

            # Calculate duration if issue was closed

            duration = calculate_duration(created_time, closed_time) if closed_time else 0

            issue_data.append((created_at, title, created_time, closed_time, duration))


    return issue_data


def calculate_duration(start_time, end_time):

    """Calculate duration in hours between start and end time."""

    fmt = "%Y-%m-%dT%H:%M:%SZ"

    start_dt = datetime.strptime(start_time, fmt)

    end_dt = datetime.strptime(end_time, fmt)

    return round((end_dt - start_dt).total_seconds() / 3600, 2)


def write_csv(data):

    """Write data to a CSV file."""

    with open(output_file, mode='w', newline='') as file:

        writer = csv.writer(file)

        writer.writerow(["date", "description of item-incident-commit", "initial login time", "final login time", "total hours between initial and final time"])

        writer.writerows(data)


if __name__ == "__main__":

    commit_data = fetch_commits()

    issue_data = fetch_issues()

    all_data = commit_data + issue_data

    write_csv(all_data)

    print(f"Report saved to {output_file}")


Popular posts from this blog

Recent Experiments testing ChatGPT's limits and some useful prompts

Introduction ChatGPT has a lot of people excited, but it deserves this level of excitement. It has a number of faults which I list below - some with workarounds - but in general it is amazingly good. It is absolutely not for having fun chatting to a robot, it's really more like a brilliant coworker who is incredibly stupid at some quite mundane tasks, but incredibly good at more tricky tasks. Summary of findings so far.  1. API vs Interactive Version - a caution 2. Coding Strengths and Weaknesses - be very careful but very useful anyway 3. Shell Scripting - amazingly good, probably what it's best at 4. Text Summarisation - fiddly but useful 5. Spreadsheet Analysis - annoying, maybe do by hand 6. Multi-Step Instruction Handling - very annoying 7. Spellchecking and writing style/grammar - ok overall but fiddly 8. File Compatibility and Formatting - not great 9. APA References from DOIs - good 10. Reference Accuracy - bad, double-check its work 11. Tone and Style Adaptations - ex...
Read more

Testing ChatGPT on coding - a script to make CSV to ICS

 So I gave ChatGPT a task of writing a CSV to ICS convertor, to take a spreadsheet of events and turn it into individual calendar file invitations. The idea is you can make a calendar with lots of event items in a spreadsheet, and then output ICS that you can just double-click to add to your calendar automatically. So here's the spreadsheet: "Event Name","Event Start Date","Event End Date","Event Start Time","Event End Time","event description or notes","URL applicable" "Meeting with John","2024-06-10","2024-06-10","09:00","10:00","Discuss project updates.","http://example.com" And here's the script ChatGPT made. It seems to get confused with things like Daylight Savings and/or Timezone but you can fix that manually. It took some debugging and I had to copy/paste my Mac's manpage for DATE into ChatGPT, but it got it eventually. The only...
Read more

Ollama3 works - running a local LLM

Do this: curl -fsSL https://ollama.com/install.sh | sh ollama create llama3  It will then download the llama3 model, about 4.7 gb to run it: ollama run llama3  if you want it to read and summarise a textfile called textfile.txt: ollama run llama3 "Read the text file $(cat textfile.txt) and summarise the findings in one paragraph of no more than 300 words"  And here's a gui for it: https://github.com/amithkoujalgi/ollama-pdf-bot The system runs as a service (daemon) on Linux. CPU usage is high but not bad and response time much better than localGPT. It stores the model files (large LLM blobs) in  /usr/share/ollama/.ollama/models The models can be dowloaded from huggingface.io or https://ollama.com/library
Read more