rimoKR's picture
Update README.md
775999d verified
---
library_name: transformers
tags:
- github
datasets:
- lewtun/github-issues
language:
- en
base_model:
- google-bert/bert-base-uncased
---
# Model Card for Model ID
<!-- Provide a quick summary of what the model is/does. -->
This is a fine-tuned `bert-base-uncased` model for multi-label classification of GitHub issues into various tags (e.g., `bug`, `enhancement`, `documentation`, etc.).
## Model Details
- **Base model**: [bert-base-uncased](https://huggingface.co/bert-base-uncased)
- **Task**: Multi-label Text Classification
- **Labels**: 19 possible tags (e.g., `bug`, `dataset request`, `help wanted`, etc.)
- **Tokenizer**: `bert-base-uncased`
### Model Description
<!-- Provide a longer summary of what this model is. -->
This model performs multi-label classification of GitHub issues based on their content. Each issue is represented by a combination of its title, body, state, and associated comments. These components are concatenated into a single input string using the following format:
```python
if example.get("title"):
text_parts.append("Title: " + example["title"])
if example.get("body"):
text_parts.append("Body: " + example["body"])
if example.get("state"):
text_parts.append("State: " + example["state"])
comments = example.get("comments", [])
if comments:
text_parts.append("Comments: " + " ".join(comments))
return {"text": " \n ".join(text_parts)}
```
The resulting "text" field serves as the input to the model. Each text entry is tokenized using the Hugging Face bert-base-uncased tokenizer with the following configuration:
```python
tokenizer(
example["text"],
padding="max_length",
truncation=True,
max_length=512
)
```
The target labels are constructed as a binary vector of length 19, where each element corresponds to one of the predefined GitHub
issue tags (e.g., bug, enhancement, documentation, etc.). Each element in the vector is set to 1 if the tag is present for the issue, and 0 otherwise. This format enables the model to perform multi-label classification, allowing it to assign multiple relevant tags to a single GitHub issue.
### Model Sources [optional]
<!-- Provide the basic links for the model. -->
- **Repository:** [More Information Needed]
- **Paper [optional]:** [More Information Needed]
- **Demo [optional]:** [More Information Needed]
## Uses
<!-- Address questions around how the model is intended to be used, including the foreseeable users of the model and those affected by the model. -->
### Direct Use
<!-- This section is for the model use without fine-tuning or plugging into a larger ecosystem/app. -->
[More Information Needed]
### Downstream Use [optional]
<!-- This section is for the model use when fine-tuned for a task, or when plugged into a larger ecosystem/app -->
[More Information Needed]
### Out-of-Scope Use
<!-- This section addresses misuse, malicious use, and uses that the model will not work well for. -->
[More Information Needed]
## Bias, Risks, and Limitations
<!-- This section is meant to convey both technical and sociotechnical limitations. -->
[More Information Needed]
### Recommendations
<!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
Users (both direct and downstream) should be made aware of the risks, biases and limitations of the model. More information needed for further recommendations.
## How to Get Started with the Model
Use the code below to get started with the model.
[More Information Needed]
## Training Details
### Training Data
<!-- This should link to a Dataset Card, perhaps with a short stub of information on what the training data is all about as well as documentation related to data pre-processing or additional filtering. -->
[More Information Needed]
### Training Procedure
<!-- This relates heavily to the Technical Specifications. Content here should link to that section when it is relevant to the training procedure. -->
#### Preprocessing [optional]
[More Information Needed]
#### Training Hyperparameters
- **Training regime:** [More Information Needed] <!--fp32, fp16 mixed precision, bf16 mixed precision, bf16 non-mixed precision, fp16 non-mixed precision, fp8 mixed precision -->
#### Speeds, Sizes, Times [optional]
<!-- This section provides information about throughput, start/end time, checkpoint size if relevant, etc. -->
[More Information Needed]
## Evaluation
<!-- This section describes the evaluation protocols and provides the results. -->
### Testing Data, Factors & Metrics
#### Testing Data
<!-- This should link to a Dataset Card if possible. -->
[More Information Needed]
#### Factors
<!-- These are the things the evaluation is disaggregating by, e.g., subpopulations or domains. -->
[More Information Needed]
#### Metrics
<!-- These are the evaluation metrics being used, ideally with a description of why. -->
[More Information Needed]
### Results
[More Information Needed]
#### Summary
## Model Examination [optional]
<!-- Relevant interpretability work for the model goes here -->
[More Information Needed]
## Environmental Impact
<!-- Total emissions (in grams of CO2eq) and additional considerations, such as electricity usage, go here. Edit the suggested text below accordingly -->
Carbon emissions can be estimated using the [Machine Learning Impact calculator](https://mlco2.github.io/impact#compute) presented in [Lacoste et al. (2019)](https://arxiv.org/abs/1910.09700).
- **Hardware Type:** [More Information Needed]
- **Hours used:** [More Information Needed]
- **Cloud Provider:** [More Information Needed]
- **Compute Region:** [More Information Needed]
- **Carbon Emitted:** [More Information Needed]
## Technical Specifications [optional]
### Model Architecture and Objective
[More Information Needed]
### Compute Infrastructure
[More Information Needed]
#### Hardware
[More Information Needed]
#### Software
[More Information Needed]
## Citation [optional]
<!-- If there is a paper or blog post introducing the model, the APA and Bibtex information for that should go in this section. -->
**BibTeX:**
[More Information Needed]
**APA:**
[More Information Needed]
## Glossary [optional]
<!-- If relevant, include terms and calculations in this section that can help readers understand the model or model card. -->
[More Information Needed]
## More Information [optional]
[More Information Needed]
## Model Card Authors [optional]
[More Information Needed]
## Model Card Contact
[More Information Needed]